Update from 5.11 to 6.0 (likely to be db update) issues

@thitinan,

Thank you for the feedback. Let’s figure it out.

You’ve mentioned that the update failed. My best guess is that under “update failed” you mean migration scripts failed. If that is the case, do you see a notification on the AAM page that states so? If yes, can you share the error log that you can download from that notification?

This way I can see all the settings that you have and what exactly failed.

If you do not want to share any information that you might find sensitive, you can submit your topic on the AAM forum or send us email directly. For more details check our plugin’s support page https://aamplugin.com/support

Regards,
Vasyl

After it went failed, I saw only the fail message in the plugin page, but after that in the AAM settings, I didn’t see any error.

If there is any logs file remain, you can name the file, and I’ll try checking on it.

Oh @thitinan,

It seems like you have some sort of PHP error. If you have access to the PHP error log on your server, you can download it and sent it to us for analysis.

Keep me posted.
Vasyl

As far as I can share will be below.
Not sure if this is the part or not, but for today it seems like it is.

[Wed Nov 20 08:58:55.319455 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: PHP Fatal error:  Uncaught Error: Class 'AAM_Core_Server' not found in /home/example/example.com/public_html/wp-content/plugins/advanced-access-manager/application/Shared/Manager.php:71, referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319524 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: Stack trace:, referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319529 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #0 /home/example/example.com/public_html/wp-includes/class-wp-hook.php(286): AAM_Shared_Manager->checkForUpdates(Array, Array, 'https://api.wor...'), referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319534 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #1 /home/example/example.com/public_html/wp-includes/plugin.php(208): WP_Hook->apply_filters(Array, Array), referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319539 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #2 /home/example/example.com/public_html/wp-includes/class-http.php(436): apply_filters('http_response', Array, Array, 'https://api.wor...'), referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319543 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #3 /home/example/example.com/public_html/wp-includes/class-http.php(596): WP_Http->request('https://api.wor...', Array), referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319548 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #4 /home/example/example.com/public_html/wp-includes/http.php(187): WP_Http->post('https://api.wor...', Array), referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319553 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #5 /home/example/example.com/public_html/wp-includes/update.php(376): wp_remote_post('https://api.wor...', Array), referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319557 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #6 /home/example/example.com/public_html/wp-includes/class-wp-hook.php(284): wp_update_plugins(), referer: https://example.com/wp-admin/plugins.php
[Wed Nov 20 08:58:55.319564 2019] [fcgid:warn] [pid x:tid y] [client ip:port] mod_fcgid: stderr: #7 / in /home/example/example.com/public_html/wp-content/plugins/advanced-access-manager/application/Shared/Manager.php on line 71, referer: https://example.com/wp-admin/plugins.php

FYI, I was using WP5.2.3, lotta plugins not support 5.3 yet, so I decided to keep that, and also need some test.

6.0.1 still the problem exists, but a lil bit change.

The image still cannot be viewed as visitor.
The hidden files/redirect files now get 404.

• This reply was modified 5 years, 3 months ago by thitinan.

@thitinan,

The AAM_Core_Server issue is described in greater details here https://forum.aamplugin.com/d/358-uncaught-error-class-aam-core-server-not-found/9.

When it is coming to managing access to media files, AAM 6 no longer has this feature in the base plugin.

I’m going to submit a new plugin “AAM Media Access Control” to the official WP repository shortly.

Regards,
Vasyl

Hi,

Thank you for the response, but I still get the same error after updated to 6.0.3.

The images cannot be viewed as visitors, and the file which is set as not be able to read by visitors got 404.

I couldn’t find any error in the error logs.

Regards.
Thitinan

@thitinan,

Oh, well you have two different problems in one topic. So the first issue with fatal error already has been resolved.

The second issue that you are experiencing is related to media access controls. AAM 6.x.x, removes the media access control feature from its core due to non-negotiable rules and we just submitted a free plugin to the official WP repository that adds this feature.

You can find more information about this from the following article https://aamplugin.com/article/how-to-manage-access-to-the-wordpress-media-library

Regards,
Vasyl

@vasyltech,

I tried the AAM6.0.4, and te AMM Protected Media Files.

Some files can be downloaded as visitor.
Some files led to 401.

Regards.
Thitinan

@thitinan,

That is the intended behavior. For restricted AAM files, AAM returns 401 Unauthorized. Please double-check your access settings for files.

If .htaccess was configured correctly, then all the files should be handled the same way.

Keep me posted.
Vasyl

@vasyltech,

The below is my .htaccess. The comment is from the version before.

# BEGIN AAM Media Access Control
<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} -f
    # RewriteCond %{REQUEST_URI} \.(jpg|jpeg|png|svg|gif|ico|pdf|doc|docx|ppt|pptx|pps|ppsx|odt|xls|xlsx|psd|zip)$
    RewriteCond %{REQUEST_URI} wp-content/uploads/(.*)$
    RewriteRule . /index.php?aam-media=1 [L]
</IfModule>
# END AAM Media Access Control

The settings, I recheck, and reconfig for visitor is

RESTRICTED
Restrict direct access to the post. Any attempt to access the post will be denied and redirected based on the Access Denied Redirect rule.

For visitor access denied redirect, I set it to (also re-set it)

Redirected to existing page (select from the drop-down)

That should be enough settings ?

Regards,
Thitinan

@vasyltech,

I found out at the file aam-protected-media-files/application/Handler.php:82.

...
if ($media->is('restricted')) {
   http_response_code(401); exit;
} else {
...

That line doesn’t read anything or redirect to any rules/settings, but 401 then exit.

Regards,
Thitinan

@thitinan,

We’ll update AAM Protected Media Files plugin to honor AAM Access Denied Redirect rules. The new update is coming shortly.

Thank you,
Vasyl

@vasyltech,

Thank you for the update.

I enabled the “Invoke Access Denied Redirect”, but the restrict document access returns 404.
The redirect setting which affect the redirect is “404 Redirect” not “Access Denied Redirect”.

Thank you,
Thitinan

• This reply was modified 5 years, 2 months ago by thitinan.
• This reply was modified 5 years, 2 months ago by thitinan.

@vasyltech,

Last update works so well.
Thank you for your support.

Thitinan