Front end theme error after upgrading to 4.7.3

[clickco]

Hello,

We ran v4.7.3 update on October 21. Thereafter, we noticed that the front-end of the forum was throwing an error (visible only to admin).



The error indicated that two templates were incompatible with this version, so I went through and changed those particular templates back to default.

The changes I made have no effect. From there, I tried setting some other customized templates back to default, just in case. Again, no changes manifested. I tried switching over to the default theme entirely. This, again, had no apparent change. We tried disabling plugins as well without effect. In short, for some reason, no changes we were making were having any effect on the front-end (even with cache clears), though the files and settings we adjusted APPEARED to stick on the back-end.

I ended up just switching everything back to status quo for the time being. In investigating some of the support threads on your forum, we thought it might all have to do with “template disk caching.” We have (and have always had) this enabled in Advanced Configuration, and pursuant to some notes we saw in other discussions, our server admin disabled a server opcache (php module) in case that was affecting PHP write permissions. Next, we tried changing the permissions of the uploads folder (also ultimately intending to do the same with datastore and applications) from 755 to 775.

However, while waiting for the uploads folder permissions change to finish processing, we ended up discovering that changing the theme back to default (which did not manifest when we had checked in previous attempts), DID render on the front-end for non-admin (and logged out) accounts.

In sum -
* Only admin are seeing the custom theme template error messages (as expected)
* Admin changes to those templates (including changing them back to default entirely) have no visual or functional effect if viewed from an admin account
* Implementing the default theme altogether also has no visual or functional effect as viewed from an admin account
* We tried disabling all plugins
* Our server admin disabled a server opcache (php module) in case that was related to the issue
* We then began trying to change permissions of uploads/datastore/application from 755 to 775 but halted upon realizing the issue seems to be different for admin vs non-admin accounts
* Related, admin views of the support tool indicates the use of a custom template EVEN when the default template is active (and shows a green check in the templates are)
* Back-end changes, including activation of the default template, DO seem to be visible from non-admin accounts

The only other admin notification we could see (and unsure if this would be related) is the following:



However, logs show the following:

Any further ideas as to how we should proceed to resolve this error?

Thank you for your assistance. 

[Meddysong]

A-ha. Some of us have been having the same experience when a particular app is activated, even though the author can't replicate for himself. (The only real difference I can discern is that we're using PHP 8 whilst he's on 8.1.)

I'm not sure what you can do but I'll be monitoring this thread to check, and should I come across a resolution in the other, I'll paste a link here.

Edited November 1, 2022 by Meddysong

[Jim M]

There is a bug causing a template error in 4.7.3 which, looking at your system log is an error you're encountering here. There is a fix for this in 4.7.4 which is beta right now and expected to be fully released tomorrow.

Your other issue about the updateCheck task, it appears to be timing out on your server or there is something blocking it. This is due to when executing the task manually, it is resulting in a 404 not found error on your server. Few things you will want to check:

1. Your server can make outbound, external connections.
2. If you are running mod_security, please disable this temporarily.

[Meddysong]

Confirming that upgrading to 4.7.4 fixed the similar error on my site. How about you, @clickco?

[Marc Stridgen]

56 minutes ago, Meddysong said:

Confirming that upgrading to 4.7.4 fixed the similar error on my site. How about you, @clickco?

Thank you for the confirmation 🙂 

[clickco]

1 hour ago, Meddysong said:

Confirming that upgrading to 4.7.4 fixed the similar error on my site. How about you, @clickco?

That's great to hear. I'm not yet seeing the option to upgrade on our site -- will continue checking throughout the day.

[Randy Calvert]

8 minutes ago, clickco said:

That's great to hear. I'm not yet seeing the option to upgrade on our site -- will continue checking throughout the day.

You can force an upgrade check by going to ACP - System - Site Features - Applications 

Click on “Check for Updates”. This will check for core updates as well as for updates to third party resources installed through Marketplace. 

[clickco]

6 minutes ago, Randy Calvert said:

You can force an upgrade check by going to ACP - System - Site Features - Applications 

Click on “Check for Updates”. This will check for core updates as well as for updates to third party resources installed through Marketplace. 

Thanks for the tip!

[clickco]

23 hours ago, Jim M said:

There is a bug causing a template error in 4.7.3 which, looking at your system log is an error you're encountering here. There is a fix for this in 4.7.4 which is beta right now and expected to be fully released tomorrow.

Your other issue about the updateCheck task, it appears to be timing out on your server or there is something blocking it. This is due to when executing the task manually, it is resulting in a 404 not found error on your server. Few things you will want to check:

1. Your server can make outbound, external connections.
2. If you are running mod_security, please disable this temporarily.

 

2 hours ago, Meddysong said:

Confirming that upgrading to 4.7.4 fixed the similar error on my site. How about you, @clickco?

Thanks so much, upgrading to 4.7.4 fixed the issue for us as well!

[Jim M]

You're very welcome! Glad to here your issue is resolved.