Some links not working after upgrade from 3.1.6 to 3.2.2

[Charles L. Cotton]

what it boils down to is that if you did not change anything and the board changes that leaves your host having changed something.

you should contact them to see what they may have done to cause this .

robert

The problem began immediately with the upgrade from 3.1.6 to 3.2.2. The only change I made was after the update. I changed the config file in response to Mick's suggestion to change "mysql to mysqli" to resolve a database update problem. The site is on a dedicated server and I've been told there have been no changes in recent months.

Chas.

[Mick]

Note that Force server URL settings and Cookie secure are two different things. Generally Force server URL settings is set to no.

[Charles L. Cotton]

Note that Force server URL settings and Cookie secure are two different things. Generally Force server URL settings is set to no.

You're right; I typed the wrong setting in my post. I should have typed "Cookie Secure." When that is enabled, most people cannot log in if they are using Firefox, Chrome and possibly other browsers.

Nothing I have tried has worked and I confirmed that nothing on my server was changed after I updated from 3.1.6 to 3.2.2. Is it possible for me to simply delete the extraneous code that is being injected? If so, where can I find it?

Thanks,
Chas.

[GanstaZ]

What happens if you disable urlrewrite?

[Mick]

"Cookie Secure." When that is enabled, most people cannot log in if they are using Firefox, Chrome and possibly other browsers.

Thats probably because you’re allowing your users to go in via http, they should only be using https if ssl is being used. You need to put a redirect in your .htaccess file to make sure all http requests go via https then turn cookie secure on. There is a ton of information about this both here and on the web.

This is what I use in my .htaccess file on my test board to rewrite http to https which was a fresh installation on an SSL server:

Code: Select all

#Rewrite everything to https
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

I can't vouch for the code but it works fine, it came from my host. DON’T duplicate RewriteEngine on when you edit .htaccess.

If you’re not sure about this speak to your host.

[Charles L. Cotton]

What happens if you disable urlrewrite?

Nothing changes.

Chas.

[Charles L. Cotton]

"Cookie Secure." When that is enabled, most people cannot log in if they are using Firefox, Chrome and possibly other browsers.

Thats probably because you’re allowing your users to go in via http, they should only be using https if ssl is being used. You need to put a redirect in your .htaccess file to make sure all http requests go via https then turn cookie secure on. There is a ton of information about this both here and on the web.

This is what I use in my .htaccess file on my test board to rewrite http to https which was a fresh installation on an SSL server:

Code: Select all

#Rewrite everything to https
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

I can't vouch for the code but it works fine, it came from my host. DON’T duplicate RewriteEngine on when you edit .htaccess.

If you’re not sure about this speak to your host.

Thanks Mick, that seems to have taken care of the login issue when Cookie Secure is enabled.

Regards,
Chas.

[Charles L. Cotton]

Here is some additional information that is puzzling.

The link problem (ex. pages: Copyright notice, Mission, Forum Rules) is somewhat intermittent. Very infrequently clicking one of the pages will return the proper page. This is less than 5% of the time. The extraneous code being inserted is "app.phpindex.php," or something similar, even with this code in the .htaccess file:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ app.php [QSA,L]

If I strip the extraneous code from the URL, the correct page is returned. I can then click on any of the pages and it returns the correct page. As soon as I click the logo and go back to the home page, the link is again broken and the extraneous code is inserted.

I did the same test using the report post feature. I stripped out "/app.phpviewtopic.php" and the post report form is displayed. I can then click any of the pages and the proper page is displayed. As soon as I go back to the home page, or select a post from the "New Posts" link, the pages and report post link are again broken.

Chas.

[Charles L. Cotton]

I found that someone else had the identical problem (plus a migration problem). Here is the link: viewtopic.php?f=556&t=2464836&start=15

I'm checking with my host to see if the package that resolved his problem (pg. 2 of the thread) will work for me.

Chas.

[Charles L. Cotton]

I found that someone else had the identical problem (plus a migration problem). Here is the link: viewtopic.php?f=556&t=2464836&start=15

I'm checking with my host to see if the package that resolved his problem (pg. 2 of the thread) will work for me.

Chas.

UPDATE:

My problem was solved by adding the package referenced on Page 2 of the above-listed link. I hope this helps someone else if they run into the same problem.

Chas.