HMWG (Free ver) possible bug
-
I have been having an odd issue lately that seems to only affect the places changed by HMWG specially the wp-admin area. Normally everything works fine and but certain pages like admin/post.php?post=38&action=edit (which is basically the admin path but changed with HMWG active to change the admin directory) would show only a “Sorry, you are not allowed to edit posts in this post type.” this happens only in other specific areas but usually are all within wp-admin/* that seem to need some hidden permission(?) that I can’t see. after doing some digging into my docker logs and changing a LOT of nginx configs I have narrowed it down using the only error that appears (and only with HMWG active) when using the rewritten urls
[error] 23#23: *1225 FastCGI sent in stderr: "PHP message: PHP Warning: Undefined array key 1 in /var/www/html/wp-includes/vars.php on line 32" while reading response header from upstream
when going to this place in the file it seems to be this;// On which page are we? if ( is_admin() ) { // wp-admin pages are checked more carefully. if ( is_network_admin() ) { preg_match( '#/wp-admin/network/?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches ); } elseif ( is_user_admin() ) { preg_match( '#/wp-admin/user/?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches ); } else { preg_match( '#/wp-admin/?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches ); } $pagenow = $self_matches[1]; $pagenow = trim( $pagenow, '/' ); $pagenow = preg_replace( '#\?.*?$#', '', $pagenow ); if ( '' === $pagenow || 'index' === $pagenow || 'index.php' === $pagenow ) { $pagenow = 'index.php'; } else { preg_match( '#(.*?)(/|$)#', $pagenow, $self_matches ); $pagenow = strtolower( $self_matches[1] ); if ( '.php' !== substr( $pagenow, -4, 4 ) ) { $pagenow .= '.php'; // For <code>Options +Multiviews</code>: /wp-admin/themes/index.php (themes.php is queried). } } } else { if ( preg_match( '#([^/]+\.php)([?/].*?)?$#i', $_SERVER['PHP_SELF'], $self_matches ) ) { $pagenow = strtolower( $self_matches[1] ); } else { $pagenow = 'index.php'; } }and its breaking at the
$pagenow = $self_matches[1];part.
This is honestly all I could find after 20 hours of searching
I have made sure all my file permissions are correct. Nginx is correct and doesn’t not block anything it seems to just be when this plugin with the wordpress panel. I hope we could find a fix for this as i love this plugin and constantly typing in “wp-admin” over my rewritten address is getting a bit annoying :/
note: yes i tried downgrading. did not work.
-
I have attempted to do both but it still seems to come up with this error and seems to only happen when the rewrite on the wordpress admin panel is active (as when testing without does allow me to edit pages and anything else restricted. even changing the path in the web bar to the default wp-admin while its still active even lets it work oddly) i have also tried this on both php7.4 and php8.0.
EDIT: Just found it actually happens with the “Health Check & Troubleshooting” plugin too. path: admin/tools.php?page=health-check&tab=tools
I also found somewhere that explained what was happening but gave no good fixes that I have tried. It said that wordpress is not recognizing you as an admin when this happens and i was wondering if it had to do with the path being changed or not.EDIT 2: tried turning on the XSS protection in the HMWG plugin grasping at straws to see if I missed anything and it still keeps the same error.
So i did some testing with switching settings and so far haven’t gotten it to work just yet. still not sure why but I think somehow the rewritten path may have some stuff that doesn’t like wordpress 5.9.2? let me look through the change logs and see if they did anything that could have changed or messed with permissions (i will do this for the docker containers for wordpress too as i used those before i switched to just a normal php container)
EDIT 1: nothing really stood out other than I saw it had security updates for 5.9.2 and that these packages were updated
@wordpress/[email protected] @wordpress/[email protected] @wordpress/[email protected] @wordpress/[email protected]doubt it would do this though as others have not had this issue before.
I have tested changing the path to backend-panel and it did not change the result. i also custom host everything in docker container and ensured there is no restrictions with nginx and php (and proof of this is that it even shows the “Sorry, you are not allowed to edit posts in this post type.” as this is something with wordpress somehow. its possible its php but i am doubtful as there is nothing there that would block it with my configs)
i should also mention this happens on two of my similarly configured sites (on the nginx and php part but the wordpress is different for both as they were made at two very different times.
- The topic ‘HMWG (Free ver) possible bug’ is closed to new replies.
