WOOCS Not compatible with plugin "All Products for WooCommerce Subscriptions"
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from Pablo Borysenco on May 17, 2021, 09:49Hello
child theme caused the site not to work properly. - it means you are doing something wrong
In any case, I cannot influence the work of the developers. I gave them all the information
Hello
child theme caused the site not to work properly. - it means you are doing something wrong
In any case, I cannot influence the work of the developers. I gave them all the information
Quote from Pablo Borysenco on July 13, 2021, 11:30Hello
Unfortunately, the developers will not change this code in the plugin.
In your case, you should hire a third-party developer to override this JS function.
Hello
Unfortunately, the developers will not change this code in the plugin.
In your case, you should hire a third-party developer to override this JS function.
Quote from cas on July 14, 2021, 07:19After all this time being patient, now they won't help me by making it compatible with the other plugin. All they have to do is put a check to jump over that code you had me remove so it doesn't get overridden on each release. Come on, help me!
After all this time being patient, now they won't help me by making it compatible with the other plugin. All they have to do is put a check to jump over that code you had me remove so it doesn't get overridden on each release. Come on, help me!
Quote from Pablo Borysenco on July 14, 2021, 11:29Hello
customization of the code is not included in the support
I gave you a solution. Also link to the documentation on how to apply this solution.
If you have no experience in programming and you cannot follow the recommendations in the documentation you should hire a programmer.
To implement this solution, there is no need for specific knowledge of my plugin(from my side, I gave all the necessary information) this is basic knowledge of wordpress
Hello
customization of the code is not included in the support
I gave you a solution. Also link to the documentation on how to apply this solution.
If you have no experience in programming and you cannot follow the recommendations in the documentation you should hire a programmer.
To implement this solution, there is no need for specific knowledge of my plugin(from my side, I gave all the necessary information) this is basic knowledge of wordpress
Quote from cas on July 14, 2021, 19:32I'll just use a different plugin since after I waited 5 months that you told me to wait, you then decide not to help me by making your plugin compatible Why didn't you just tell me immediately that you wouldn't do it? Why make me wait 5 months? That's not nice to do to someone.
I'll just use a different plugin since after I waited 5 months that you told me to wait, you then decide not to help me by making your plugin compatible Why didn't you just tell me immediately that you wouldn't do it? Why make me wait 5 months? That's not nice to do to someone.
Quote from Pablo Borysenco on July 15, 2021, 11:31Hello
I helped you, I gave you a solution. We did a free research and solved the problem of incompatibility with third-party plugin. We've wasted our resources
I didn’t promise you to embed this code in our plugin. - https://share.pluginus.net/image/i20210715122533.png and https://share.pluginus.net/image/i20210715122644.png - The developers decided not to embed this code, because there is a risk of breaking the plugin for other users
Hello
I helped you, I gave you a solution. We did a free research and solved the problem of incompatibility with third-party plugin. We've wasted our resources
I didn’t promise you to embed this code in our plugin. - https://share.pluginus.net/image/i20210715122533.png and https://share.pluginus.net/image/i20210715122644.png - The developers decided not to embed this code, because there is a risk of breaking the plugin for other users
Quote from cas on July 15, 2021, 17:17You did not offer a "real" fix, you offered a bandaid to create a Child theme to segregate your program so your plugin updates wouldn't override the code fix I applied, but this was supposed to be "temporary" until your developers would make your plugin compatible. You told me you submitted the recommendation to your developers and were waiting on them, and thus that kept me waiting for 5 months too! Correct?
And by putting your program in a Child theme, yes, that stops it from getting overridden when new updates come out, but when plugin updates come out, then I have to spend the rest of my life dealing with your bandaid fix, because I would have to check every time if that program got updated and I would have to manually update my child theme program to have the latest updates, rather than your developer doing the right thing and just making your plugin compatible from the start by adding an IF statement to see if that other plugin was active, and if so, then jump over that section of code you had me remove. Simple fix, so why not do it?
Do you understand how your bandaid fix would leave me having to do manual maintenance on your plugin every time an update came out to get the latest features? And that would be forever. Please ask the developers to do the right thing.
You did not offer a"real" fix, you offered a bandaid to create a Child theme to segregate your program so your plugin updates wouldn't override the code fix I applied, but this was supposed to be"temporary" until your developers would make your plugin compatible. You told me you submitted the recommendation to your developers and were waiting on them, and thus that kept me waiting for 5 months too! Correct?
And by putting your program in a Child theme, yes, that stops it from getting overridden when new updates come out, but when plugin updates come out, then I have to spend the rest of my life dealing with your bandaid fix, because I would have to check every time if that program got updated and I would have to manually update my child theme program to have the latest updates, rather than your developer doing the right thing and just making your plugin compatible from the start by adding an IF statement to see if that other plugin was active, and if so, then jump over that section of code you had me remove. Simple fix, so why not do it?
Do you understand how your bandaid fix would leave me having to do manual maintenance on your plugin every time an update came out to get the latest features? And that would be forever. Please ask the developers to do the right thing.
Quote from Pablo Borysenco on July 16, 2021, 11:46Hello
And by putting your program in a Child theme, yes, that stops it from getting overridden when new updates come out, - YeS! And after that you don't need to change anything anymore! It will not be affected by plugin and theme updates
Hello
And by putting your program in a Child theme, yes, that stops it from getting overridden when new updates come out, - YeS! And after that you don't need to change anything anymore! It will not be affected by plugin and theme updates
Quote from cas on July 16, 2021, 17:54I think you missed the important part I wrote about when that program gets updated, my version of the program in the Child theme will need to be manually updated by me forever, correct? This is why you should make it compatible and not put that forever maintenance work on us.
I think you missed the important part I wrote about when that program gets updated, my version of the program in the Child theme will need to be manually updated by me forever, correct? This is why you should make it compatible and not put that forever maintenance work on us.
Quote from Pablo Borysenco on July 19, 2021, 12:25Hello
my version of the program in the Child theme will need to be manually updated by me forever, correct? - Why? I gave you a solution(https://share.pluginus.net/image/i20210719132421.png). With this solution, you only need to change the code once. And I will repeat to you again - updates of the main theme or any plugin do not delete this solution.
Hello
my version of the program in the Child theme will need to be manually updated by me forever, correct? - Why? I gave you a solution(https://share.pluginus.net/image/i20210719132421.png). With this solution, you only need to change the code once. And I will repeat to you again - updates of the main theme or any plugin do not delete this solution.
Quote from cas on July 19, 2021, 16:59You don't understand my comment. I said when your plugin changes, IF I want to have the latest code, then I will need to manually update the code in the Child theme to have your plugin's latest code, correct? If I don't wish to have the latest plugin code for that program in the Child theme, then I can just let it alone, but that's not wise to do if there are any security and feature enhancements, correct?
You don't understand my comment. I said when your plugin changes, IF I want to have the latest code, then I will need to manually update the code in the Child theme to have your plugin's latest code, correct? If I don't wish to have the latest plugin code for that program in the Child theme, then I can just let it alone, but that's not wise to do if there are any security and feature enhancements, correct?
Quote from Pablo Borysenco on July 20, 2021, 11:57Hello
You only need to override one function. The likelihood that we will change it is less than a third-party developer will change the plugin code and the compatibility will not work
Hello
You only need to override one function. The likelihood that we will change it is less than a third-party developer will change the plugin code and the compatibility will not work
Quote from cas on July 20, 2021, 17:34Glad you now see why I waited all this time for it to be made compatible so i don't have to take that risk of that function changing in the future. But unfortunately I waited for nothing. I'll use anther plugin that is compatible. I found one. Take care.
Glad you now see why I waited all this time for it to be made compatible so i don't have to take that risk of that function changing in the future. But unfortunately I waited for nothing. I'll use anther plugin that is compatible. I found one. Take care.
Quote from Pablo Borysenco on July 21, 2021, 09:57Hello
Great! I'm glad you found a good solution
Hello
Great! I'm glad you found a good solution