Dev Tools - Getting Maximum execution time of 30 seconds exceeded error after upgrade to vr. 3.0.4 #831
-
Hi, When I try to change the max_execution_time to 120 it still doesn't work. I've also removed all paths from config/devtools.php. If I downgrade to version 2.0.X it works, but not usable (buttons are misplaced and checkboxes cannot be checked). I am on Laravel 10.43 - recently upgraded Any help would be really appriciated. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 2 replies
-
Hello @webteamseo Have you been able to try a clean install? i just installed and there is no problem with the operation:
There is the version i try. Cheers. |
Beta Was this translation helpful? Give feedback.
-
Hi, I didn't run it on clean install. What I am trying to understand if it is possible that my project is too big so version 3.0.4 takes too much to load. I tried changing the devtools.php under config, to remove paths, but still this issue persist. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Sorry for taking time to get back here and for the video. I will come back with news or with additional queries, like "Now, please do video a reproducing the bug, but you need to sing the problem like you have 99". hehe 😺 Cheers, and sorry again 🙏 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Yes! it was worth waiting :) it works now. The problem was folder named devtools under resources/views/vendor/backpack |
Beta Was this translation helpful? Give feedback.
So, I have good news, and bad news.
Good news is that I couldn't reproduce the issue. Bad news, is that I recall seeing those broken things before we launched v3 of devtools.
I've just installed the tool now:
Question 1: can you confirm that when you install devtools you get the same versions of those packages ?
Here are the coreui-v4 and theme-tabler working as expected:
So .. I suspected of 2 things:
1 - You may have the files overwritten in your
resources
folder. If that's the case, you are not getting the updated versions of the files from the vendor.2 - Your css/js/views are cached and you are not loading the correct files when changing themes.
For 1, I would just look into your
r…