Some plugins from the directory cause errors or have misstypos in code,
if there is no easy way to report issues for each particular plugin,
Fatal error: Allowed memory size of 268435456 bytes exhausted
(tried to allocate 135168 bytes) in ... on line 238
Every plugin listed in the directory has a repository on GitHub, and that is the best place to submit an issue.
Also the forum can be used to report something that is not working.
Microsoft Github is not for end-users,
The result is, you don’t even know how many plugins currently presented in directory causes errors like the one mentioned before.
Agree. This is why I also mentioned that this forum is an alternative.
I recently created an Issue at GitHub, suggesting a Tested up to header, so it’s more clear for users if a plugin works with recent version(s) of CP.
On the other hand, maybe they should all work, because no breaking changes have been made to the CP codebase, as far as I know..
the error mentined above I found in this one
before I checked another one, there was wrong names in some actions/hooks, so the desired functionality does not appeared in admin panel, but it was not even described about what the plugin do.
Of course we could say, if there would be more users, we could receive feedback more often, and then fix them or take down some of them… But the point is, we should first provide easy to use and professional looking plugins-repo, with TLDR and KISS aproach, good navigation, easy way to report issues and possibility to read the previously written by others etc… then to think about inviting more users, otherwise I’m afraid the scenario around plugins may discourage them from the very begining.
The shortcode of this plugin is also causing an error in the frontend of my site.
Besides GitHub there should be a “report” button at each plugin/theme page, so user can report a (fatal) error. Besides not using GitHub the repo can be abandoned by the dev.
On the other hand, pretty certain the CP Plugin/Theme Team doesn’t want to receive unrelated reports, so this is something that should be looked at first.
plugins by Azurecurve are badly coded (they don’t have deactivation hooks set correctly for example and when I asked why they told me that basically they were plugins they use on client sites and they don’t want the client to uninstall them accidentally).
Azurecurve was an active member of the community but went away for a disagreement of opinions.
Some people think those plugins should be removed or forked and corrected and maintained by some other dev - and I agree - but as of now nothing has been decided about them.
In may azurecurve pushed updates to his plugins to make them comply with the directory.
At now I’ve some of my plugins that can be used as a replacement for azurecurve’s ones.
Thanks for confirming they did indeed update them.
Although plugin is updated, the shortcode is (still?) causing an error, so that needs some work.
Fatal error: Uncaught Error: Xdebug has detected a possible infinite loop
There’s not much activity at the GH page, so posting there will not help I think.
For Breadcrumbs,
in /azrcrv-breadcrumbs/azrcrv-breadcrumbs.php change line 236 to
if ($parentid !== false){
to fix the infinite loop.
That’s strange, !== false doesn’t work for me but != false does?
And I now see it’s not caused by the shortcode alone, it’s a global error.
For me, after changing the PHP version to 8 and above, it causes a fatal error due to some plugins.
When I revert to PHP 7.4, everything is OK again, and after upgrading ClassicPress to the latest version, the admin interface is also slow to load.
I think I’ll stay on PHP 7.4 for now and see if I can get CP to revert to an older version.
It’s easier for me to stay on the old version of PHP than to look for plugin alternatives
And these are plugins that are a bit older because newer versions are subject to gutenberg
P.S.
Where can I download older versions of CP?
You can move between ClassicPress versions using the “Switch to ClassicPress” plugin.
CP 2.5 admin should be faster as a lot of jQuery was converted to vanilla JS.
Maybe using Query Monitor you can spot what is slowing down your installation.
Hmm somehow I noticed that pages open much faster in Mozilla firefox than in chrome.
In chrome other pages load slowly and not just CP, in Mozilla it is much faster
I don’t know why
Have you added a plugin to your Chrome browser? If so, that’s probably the cause of it being so slow.
I don’t know what add-on you’re referring to.
I have add-ons in my browser that are useful to me, such as a password manager, adblock, etc.
One of them is almost certainly the cause of your browser being so slow. You can confirm this by turning them all off and seeing if your browser is faster. If it is, try turning them on again one by one until you identify which one is the cause of your problem.
