Jose
Forum Replies Created
-
Hi @midihead
thank you for reporting this issue.
Those links have no URL. This is why if you click on them you refresh the page.
They have no URL because they are related to the editing page of whatever single post or single post type.
Let’s do an example. Let’s consider “Edit Single Post”.
Imagine you have the blog posts “Hello World!”, “Hello WordPress”, “Hello Something Else”.
When from the main admin navigation you go to Posts, and you click on “Edit” on one of those blog posts, then you are in the editing page of that post.
“Edit Single Post” is valid for the editing page of whatever blog post.
Maybe we could link it to the editing page of the last blog post. Do you think it would be better?
At the moment it links to anywhere, and it was better to make it unclickable. The fact that it is clickable even without linking to anywhere is a bug, but for me, it’s not true that in the editing page of the post, the plugins are not disabled. I’ve right now tested it again, and it works for me.
You can check the disabled plugins on the editing page of a post by doing as follows:- Go to the editing page of the post
- Right-click with your mouse
- Click on Inspect
- Click on Console
- Check the list of plugins written after “*** PLUGINS DISABLED BY FREESOUL DEACTIVATE PLUGINS ***”
If you are an administrator that have the rights to activate a plugin, you will see that information.
Please, let me know if you still think that it doesn’t work.
I’m also interested to know if you prefer to link “Edit Single Post” to the last post, or let it unlinked.If something is not clear let me know.
Have a great day!
Jose
Hi @shovonbk
From your comments I didn’t understand you were not able to see anymore the backend settings on an installation where you did use them. This was a bug. It wasn’t done on purpose.
I removed the backend settings on purpose for new installations, but not for those installations where those options were already used. Sorry for this inconvenience.
I suggest you update to v. 2.3.0. You will see again the backend settings pages. If for any reasons you still don’t see them let me know.Hi @jumbo
you can do it with the settings Custom URLs => Plugin By URL. I suggest you read here: https://freesoul-deactivate-plugins.com/how-deactivate-plugiins-on-specific-pages/plugin-by-url/
You will need to write parts of the URLs where you want WooCommerce active.
To match the processes like the checkout process, the “add to cart”…, I suggest you use *wc-ajax*In any case, I strongly suggest you to test all the WooCommerce processes after you use the Plugin By URL settings. Don’t forget also to add the endpoint URLs used by Stripe, PayPal…
Another method would be to disable WooCommerce in all the Post Types, but the products, and in all the archives, and then enable it on the WooCommerce pages. This this last method you would have less risks one of the processes don’t work.
I hope it helps.
Have a great day!
Jose
You don’t know the most used features of the plugin. I know it because I help the users, and most of them use the frontend features. Or do you think you know it better than me?
I don’t force anybody. As said, you can use a different plugin that has the backend features if for you buying a PRO license is too much money.
This is not really a decision. You decide when you can choose between different options. In this case, it’s simply not possible to go ahead with this project without money. You can say whatever you want, other users can cry all day long, but I can’t continue to work only for free.
And if I don’t see more sales, I will remove other features, or eventually remove the free version from the repository. That’s it. I hope it’s clear now.50% of the features? Really?
There are 2 features: Backend Custom URLs and Backend Singles. All the other ones are free, and they are a lot. As said who used the backend settings will still be able to use them. The difference will be ONLY ON NEW INSTALLATIONS.
I heard many times that the free version is enough and you don’t need the PRO one. Well, I need people buy the PRO version, in another case the free version can’t exist. This is why 2 features were removed from the free version, but ONLY FOR NEW INSTALLATIONS.
If this means that people give a bad review instead of buying the PRO version, the free version will totally disappear because it’s impossible to work on the free version if there are not enough sales of the PRO version. I hope this is clear for all the other users.
If FDP free without the backend settings is not enough for you, use a different plugin that gives those options.
You can install Plugin Organizer for example. It’s a very good plugin with a lot of features. There are also other very good alternatives like Plugin Load Filter.
Nobody is saying you have to use FDP. If it’s active on your site, better if you deactivate it.I suppose you are speaking about the deactivation of the plugins in the backend.
Of course, all those users who used those features still have them, even if they aren’t PRO users.
They are hidden only for new installations or if they were not used.“This is not right way do business…”. What’s your idea to do business? That other people work only for free and you use their work to earn money with your website?
Sorry, you were never a fan of FDP. I’ve never seen a nice review from you, and it doesn’t look like you were a PRO users. You have never contributed to this project.
Remember that people need to earn money for living.I will be honest. If I see other reviews like this one, FDP free will completely disappear, and only the PRO version will exist. For me, your review is totally inappropriate.
thank you for reporting this issue.
This PHP warning will dirty your debug.log file, but it has no impact on the functionality.
It will be fixed with the next version that will be published soon. I hope before 2-3 days.Until then, if your site is live, I suggest you disable the debug in wp-config.php.
Have a great day!
JoseHi @joefryfoto
you are welcome! I’m happy it worked.
About the WordFence alarm, I can only say that Freesoul Deactivate Plugins doesn’t write any .tmb directory outside the WordPress installation.
It writes the file wp-content/mu-plugins/eos-deactivate-plugins.php, and the folder wp-content/uploads/FDP. Inside the FDP folder, it stores its cache and writes its settings. Nothing else.Are you sure the .tmb is not written by something else?
Have a great day!
Jose
Hi @joefryfoto
I checked the code of the WordPress core, and it seems you can see the sentence “Network only” only if in the main comments of the plugin main file you have “Network: true”. In no other way. I think you can stop to investigate about cookies and so on.
Here the main comments of the main file of Freesoul Deactivate Plugins of the previous version 2.2.6:
<?php
/**
* Plugin Name: Freesoul Deactivate Plugins
* Plugin URI: https://freesoul-deactivate-plugins.com/
* Description: Disable plugins on specific pages for performance improvement and support in problem-solving even when you have many plugins.
* Author: Jose Mortellaro
* Author URI: https://josemortellaro.com
* Domain Path: /languages/
* Text Domain: freesoul-deactivate-plugins
* Version: 2.2.6
*
* @package Freesoul Deactivate Plugins
*/You can see it here: https://plugins.trac.www.ads-software.com/browser/freesoul-deactivate-plugins/tags/2.2.6/freesoul-deactivate-plugins.php
As you can see nowhere you see Network: true. This was working right.
Also the versions < 2.2.6 were working right.
Don’t ask me why because I have to admit that I don’t know it, and I’m also surprised to see it, the last official version 2.2.7 has the comment “Network: true”. You can see it here https://plugins.trac.www.ads-software.com/browser/freesoul-deactivate-plugins/tags/2.2.7/freesoul-deactivate-plugins.php
The issue you are experienced is caused by that comment line, nothing else. Probably in your other installations you hadn’t version 2.2.7. This will be fixed with the next release. If you want, you can edit the plugin’s main file and remove the line “Network true” to fix the issue before the next release.
I hope it helps.
Have a great day!
Jose
Hi @joefryfoto
thank you for reporting this issue and for the information.
Can you help me better understand the issue?This is what I understand:
- You have a multisite installation
- From the admin top bar you go to My Sites => Network Admin => Plugins (that should have an URL that looks like https://yoursite.com/wp-admin/network/plugins.php
- You click on “Network activate” on the action link of Freesoul Deactivate Plugins
- You see the message “Freesoul Deactivate Plugins can’t be activated networkwide, but only on each single site.”
Is it right until here?
After you see that message I suppose FDP is kept disabled on the network, right?
Then you go to the plugins page of a subsite, and for Freesoul Deactivate Plugins you see “Network only” and you don’t see the action link “Activate”. Is it right?
And it is not possible to activate Freesoul Deactivate Plugins, right?But on another multisite installation you were able to activate FDP on each subsite, right?
Please, correct me if I’m wrong.
About your sentence “installation writes nothing into mu-plugins“. If you are not able to activate FDP, this is totally normal. FDP writes into the folder wp-content/mu-plugins only if you activate it.
Please, let me know if you were able to activate FDP at least on a subsite of the network.If I haven’t understood the issue, please add more details to help me better understand it.
In the meantime, I will do some tests with multisite installations taking into account also your last comment. I can anticipate that FDP doesn’t guarantee it works with different domains. The domain has to be only one.
Have a great day!Jose
Thank you very much for the information @dkuzmicki
Thank you @dkuzmicki ??
I am happy the issue is solved.
Can you please let me know if you clicked on “deactivate” and then the ACF mu plugin disappeared, or it disappeared because you clicked on “delete”?
Because if it disappeared after you clicked on “deactivate” it would be a serious bug of MU Manager that I have to fix.Have a great day!
Jose
Hi @dkuzmicki
did you use MU Manager to delete advanced-custom-fields-pro.php, or only to deactivate it?
I mean, you clicked on “deactivate” and then the mu plugin disappeared, or it disappeared because you clicked on “delete”? In the second case there are no bugs.In any case, to solve the issue try these steps:
- Via FTP go to the folder wp-content/mu-plugins
- Look for a file that looks like advanced-custom-fields-pro.disabled-66df3c665fd24 or advanced-custom-fields-pro.deleted-66df3c665fd24
- rename that file to advanced-custom-fields-pro.php
The code 66df3c665fd24 is just an example. You will see a different code.
If you can still see the page of plugins, another way to solve the issue could be deactivating Advanced Custom Fields PRO and activate it again. By doing that it will probably write again its mu-plugin to the folder wp-content/mu-plugins.
I hope it helps. If you stil have issues let me know.
Have a great day!
Jose
Hi @talothman
thank you for reporting this issue.
First, I would be very sure the cause of the issue is the new version. Can you roll back to version 0.8 and confirm that it works again?You can go to https://www.ads-software.com/plugins/content-no-cache/advanced/, scroll down to Previous Versions, select v. 0.0.8 and click on Download.
You can also download it directly here.
Unfortunately, since they removed the Install Growth chart is very difficult to understand if the new versions give issues. We do a lot of tests, but without any statistics, a bug may be discovered after months.
In the meantime, I will try to understand the differences between v. 0.0.8 and 0.1.1 that may cause issues.
If with v. 0.0.8 it works again, I suggest you keep that version until I can provide a new version.
The versions after 0.0.8 have no security fixes, so you don’t have to worry keeping for a while v. 0.0.8.Have a great day!
Jose