I suppose you are aware of this. But if not, to inform you what Wordfence says:
Critical Problems:
* The Plugin “Admin Page Spider” has a security vulnerability.
Vulnerability Severity: 4.4/10.0 (Medium) Vulnerability Information
https://www.ads-software.com/plugins/admin-page-spider/#developers
1.) Till version 3.20 the plugin shows the correct pageorder, including correct parent – child page relations.
Version 3.30 shows all parent pages and afterwards all child pages – without parent relation. (Which makes the plugin nearly unusable.)
2.) A rollback to version 3.20 is not possible too, because in the wordpress plugin repository is only version 1.04 available (all others are lost?)
]]>After installation in a PHP 8.1 local test-environment (Local, Laragon) on https://
an error message is shown:
array offset on value of type bool in C:\ … \wp-content\plugins\admin-page-spider\apspider-wordpresspages.php on line 7
Plugin itself seems to work afterwards, but I get this error message on every described installation.
]]>Is it compatible with php8.x?
]]>Hi,
when I log in as an editor (no longer as an administrator) the 2 menus “edit pages” and “edit posts” are not present on the admin toolbar.
Could you explain why ?
Thanks !
]]>Hi,
I just installed this plug on three sites. It works great on one but doesn’t show up on the other two. All are WP sites, all running 5.2.2. I have three screencaps that will illustrate the problem.
Please view them here
Hi Jay,
I’m noticing a few PHP errors in the current code. Here’s a screenshot from Query Monitor:
Classic Editor 1.x on WP 5.0 has now two different options:
a) default editor for all users: Classic / Block
b) allow users to change editor: Yes / No
Having set a) to “Classic” and b) to “YES” does not work correct with Admin Page Spider (which delivers always Gutenberg = “Block Editor” and ignores the default setting)
Only with b) “No” Admin Page Spider works as expected and opens Classic Editor.
Please update Admin Page Spider to respect also the default = “Classic” setting when user allowed to change the Editor (b = “YES”).
]]>Hi, when clicking > ACF > View All, the page just brings up the message “Invalid post type.” (APS Pro Pack v3.6.1)
]]>Love this plugin! This might be an enhancement request but here goes… Is there an option/setting that could filter the pages/posts in the Edit drop-down?
Settings > Admin Page Spider > WordPress Pages
Display Page Type > (radio button) All (default option), Published, Drafts
Settings > Admin Page Spider > WordPress Blog/Posts
Display Page Type > (radio button) All (default option), Published, Drafts
Or possibly have the three filter options display in the Edit drop-downs themselves so users do not need to return to the plugin settings page as often.
Regards,
H
Bonjour.
Plugin bien, mais petit problème avec.
Seul admin, peut voir “Edit page” dans bar du haut (wp-admin)
Customer, Shop manager, editeur, n’est pas visible.
Pourquoi ?
Merci pour votre aide
EN :
Hello.
Plugin well, but small problem with.
Only admin can see “Edit page” in the top bar (wp-admin)
Customer, Shop manager, Publisher, is not visible.
Why ?
Thank you for your help
Hi,
When attempting to delete the plugin, it fails with a message saying “internal server error”.
This only happens with this plugin, deleting other plugins works as normal.
]]>Hi,
Like your plugin. I like WordPress admin bar which shows Edit Post link on the admin bar when am logged in and viewing a post on front end. But your plugin replaced Edit Post with Edit Pages.
Is it possible if you show both in the above case?
]]>Hi, the plugin sounds like just what I need.
Only the “View” option is visible, allowing me to navigate through the tree. I need to be able to “Edit”, am I missing something ?
Many thanks,
Steve
Hey,
Love the plugin, but 1.08 didn’t work out well – I rolled back to 1.04.
1. I didn’t care for the really narrow dropdown – plus the shortened titles were spitting out a question mark at the end of the page title if it was too long. It was more helpful to quickly find a page to edit with the wider dropdown.
2. Not crazy about changing it to ‘WordPress Pages’. I liked ‘Edit Pages’ much better. Maybe ‘Spider Admin’? The ‘WordPress Pages’ feels like a disconnect for me.
3. It also looks like the default ‘Edit Page’ link is gone too.
In summary…FWIW…my $.02
– Bring back the wider dropdown
– Change the wording back to ‘Edit Pages’ or something new like ‘Spider Admin’
– Bring back the native ‘Edit Page’
And BTW…I still think this is a fabulous plugin. Saves me a ton of time. But, for now I’ll stick with 1.04.
Thanks!
]]>Congrats on your first plugin ??
I just had a couple of suggestions.
Instead of removing the Page Builder node in wp_before_admin_bar_render, just use remove_action('admin_bar_menu', 'FLBuilder::admin_bar_menu', 999)
This would allow it to “play nice” with other plugins that may rely on that node existing and allow them to react accordingly.
Also, I noticed that in apspider_admin_bar_removal function you are not checking your plugin settings to see if those menus are hidden. For example, if I hide the “Edit in Beaver Builder” menu, it shouldn’t remove the “Page Builder” node. Currently, the only way to get that menu back is to disable your plugin.
Thanks.
]]>Hello.
This sounds like a necessary plug-in. While trying to install the plug-in, however, I got the below message.
Can you help?
Thanks!
Cameron
Plugin could not be activated because it triggered a fatal error.
Parse error: syntax error, unexpected ‘[‘ in /var/www/vhosts/trentstudios.com/subdomains/test/httpdocs/wp-content/plugins/admin-page-spider/apspider-functions.php on line 6
]]>