Roots Discourse

Can't upgrade WordPress or add new plugin using Sage 10 Theme

Hello guys, Im having issues with Sage 10 Theme, here’s the explanation:

I can’t upgrade WP or add/upgrade plugins when the theme is active in my site, the process just fails and puts the site in “maintenance mode”.

I’m trying to figure out why this happens, here some info:

  • There’s no debug messages in JS console.
  • Im sure it only happens when Sage 10 Theme is active and no other theme (Twenty Twenty etc…)
  • I’d set define(‘DISALLOW_FILE_MODS’, false); in wp-config.php (That helped some ppl with similar problem)

I’m not sure where I can start testing things in theme (file or method) to fix this issue.

Please help! Thanks in advance.

1 Like

The first thing to check would be your server logs. Something’s probably throwing an error, and that’s where it’s likely to be recorded. You might also look at Sage’s own sage.log.

1 Like

You are right! There’s a Moz Security error.

Im sorry about it, I forgot to check server logs. My bad :confused:

Now Im trying to fix this issue, I hope is not related with Sage theme.

Thanks for your time mate!

@Dioniggio I was facing same issue you mentioned in your post. Thanks man for asking in post i read this post. It really helped me a lot. :slightly_smiling_face:

Hi guys,

I’d installed a new WP from scratch along with my custom Sage 10 Theme (production server and local), and then trying to install new plugins (akismet, Classic Editor) but it keeps giving an error (Installation failed: ) and sometimes disables this page /wp-admin/plugin-install.php.

The server error logs only throws this:

[21-Apr-2021 15:34:30 UTC] PHP Warning: set_time_limit() has been disabled for security reasons in /usr/home/ on line 471

I commented this line in 471 in class-wp-upgrader.php and it worked, plugins are installing correctly.

As we all know it is not the best choice to modify WP core files. But it is the only way I found to fix the issue.

I wonder if Sage 10 Theme is causing this situation. Im not having this issue with legacy WP themes active.

I have a playground/test WP installation if you want to check it by yourself. I bring back core files to original with uncommented set_time_limit() line.

User: admin
Pass: sage10testing

PS: @alwaysblank you commented about sage.log, I never found it.

In the latest Sage 10, you’ll find acorn.log inside theme/storage/logs.
I don’t believe Sage can cause such warning, however, this version of sage doesn’t seem to tolerate warnings and it breaks the website when there’s one. Previous versions were ignoring warnings.

I’d recommend contacting the hosting company about enabling set_time_limit() which should resolve your issue without modifying core WordPress files.

This topic was automatically closed after 42 days. New replies are no longer allowed.