mikehuangsd

We recently ran into the same problem with individual password-protected pages no longer redirecting correctly for all users (for some it would work, for some it would redirect back to the site’s homepage instead of redirecting back to the protected content, and some would just see a blank page after login).

After much seemingly inconsistent behavior (same network vs off, phone vs pc, various browsers on the same pc, etc) we determined it is because the ‘referrer-policy’ directive on the web server is set to ‘strict origin’ instead of the default.

Some browsers support strict-origin (chrome, firefox) and some do not (safari, edge), leading to the inconsistent behavior. Try getting the server admin to change that to the default of ‘no-referrer-when-downgrade’-

Also, the wp-login.php page is part of the login process for these protected pages. If that page has been renamed or hidden or is otherwise not accessible for all users, that will also break the password-protect function for individual pages.

• This reply was modified 6 years, 10 months ago by mikehuangsd.
• This reply was modified 6 years, 10 months ago by mikehuangsd.

sorry – 100% user error – the thumbnails and captions are working fine now under PHP 7.

Hello-

I have been using NextGen Gallery for many years.

Recently the web server administrator upgraded to PHP 7 (from I believe PHP 5.6).

I now notice that manually modifying the thumbnails using the ‘edit thumb’ feature no longer works (it appears in the administrative interface that the thumbnails change, but in the public gallery they stay as the default and absolutely won’t change).

I also noticed that specifying ‘nggalllery=# template=caption’ no longer seems to have any effect – I don’t get captions anymore appearing below the thumbnails.

I updated the NextGen Gallery plugin to 2.2.12, with no change.

These two features still work on an identical account still running PHP 5.6.

Please let me know if you can fix these issues with PHP 7.

• This reply was modified 7 years, 6 months ago by mikehuangsd. Reason: typos

Awesome – The newest release completely fixed the problem – Now I have a pretty graph.

Thanks-

Mike

changed all tsv files yesterday to 777 – graph still not displaying. I do see the tsv files changing though (the modified date is today). is there anything else I can change?

OK – I was not aware of this bug tracking system – thank you.

From that thread, it seems the steps I need to follow are:

1) ask the web server admin if he is using Suhosin. If he is, ask him to change “suhosin.post.max_vars” and “suhosin.request.max_vars” to 5000.

2) If that doesn’t work, ask him to increase PHP execution timeout

3) If that doesn’t work, wait for WordPress version (future release)? The last entry seemed to indicate that writing a patch is not yet assigned to a WordPress developer.

Thank you

I’m the original poster – Just wanted to update everyone – It wasn’t a problem with AllowOverride in this case. My web server administrator has that set to ‘All’ by default for all accounts on his web server.

The issue was due to the fact that his server is a pretty complicated setup. He’s apparently got a front-end server, a back-end server, a proxy, and even HTTPS and HTTP run off of different machines somehow (clearly I don’t really understand his setup). But what he told me was that to get WordPress with multisite enabled to run correctly, he has to put in a special rule to tell his proxy not to try to interpret URLs, and to pass those URLs as-is back to the real server. Or something. Anyway – he’s now done that, and everything works!

Thanks for all your help. You can close this thread.

ok thank you – I will ask the server admin about the httpd.conf file and make sure AllowOverride is set to All.

Unfortunately he’s gone home for the night – I will check back in tomorrow.

OK update. I just did a clean install of wordpress multisite into a separate account on the same web server. I installed the same themes, and the same plugins. I used the same htaccess file and did everything else the same that I could think of.

Uploading pictures to the new test site, and all it’s subdirectory subsites, works just fine.

If the same htaccess file works right for the new account on the same web server, that means it’s not a httpd.conf problem, right?