Step 2: Build the list of the fetched assets and print it… This is stuck at Please Wait and never finishes.
I’ve tried disabling every plugin except Asset CleanUp and clearing all caches.
I’ve also tried to reset everything in Asset CleanUp (settings, page loads & any load exceptions) in the tools section. I removed and re-installed Asset CleanUp, but nothing seems to work. There are 10 page unloads that I originally set up that will still work if I import the settings into Asset Cleanup, but I still get stuck at step 2 above.
All plugins and WordPress are updated to the most current versions.
I do get the follwing errors (see the screenshot) when I inspect the page, but I’m not really sure what to do with the information or if it’s even helpful. This is when I’m in the Asset CleanUp settings on the “CSS & JS Manager” tab and the Fetched Asset line is trying to print, but never does. I’ve also tried “Manage in the Front-End” and it’s not working.
Any ideas?
Also tried it on their live site. Same problem. Any suggestions?
]]>When opening the plugin to create a backup, I am greeted with blue dots rotating in a circle over the most recent backup made (August 2020). When clicking on the [Backup] to begin a new backup, there is no indication that the button has been selected. the blue dots continue to rotate in a circle and nothing happens.
I am experiencing this on both the stage and live sites, and have not found a solution thus far. Is there anyone who could assist?
Thanks
J
]]>I use updraft plus on all three of my wordpress blogs (2 non password protected, and 1 that is – which is: https://www.sylumclan.com/SylumManor/wikiblog/ but its password protected) I’ve never had problems with scheduled or manual backups for any of the blogs until recently.
As of end of August (my last successful back up was Aug 7th) I couldn’t get updraft to work. I figured it was a new update so just let it go until another update and still didn’t work. No matter what size limit I put on the zips it stalled half way through whether it was 50, 100 or even 400 – still stalled.
As it was a password protected site I knew it was having a hard time communicating to wordpress so I had 207 scheduled tasks not concluded – I worked with my hosting company and set up a cron job and which worked, and that particular problem is cleared.
Yet if I manual update with updraft it’s still stalling half way through. The logs do not show why it’s lagging or stalling it just shows the last thing it was doing. It gets to a point it will say 28 seconds to next segment, then go up to almost past 100, then come back down to 8, then keep rising until hours go by and it does nothing.
I’ve never had a problem like this in the two years I’ve been using Updraft on this blog (despite it being password protected). This is a heavy information blog and I need it backed up.
What else do I need to do?
]]>Every other aspect of the wordpress part of my site works just fine. Dunno what the deal is.
Domain: passtheaux.co
]]>So I found an issue with one of my sites. After troubleshooting, my hoaster says it’s a problem with the plugin.
We found the following fatal PHP error when troubleshooting your issue earlier.
[27-May-2016 07:23:41 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /home/supppar/public_html/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-directory.php on line 136
This denotes that something within the ‘better-wp-security’ plugin was taking too long to complete, causing the site to resolve slower because of it.
Thank you
Michelle
https://www.ads-software.com/plugins/better-wp-security/
]]>I’m new to the WordPress Forum, so please excuse me if I’m not conveying the issue properly.
We have two websites that some people are having issues accessing. They are receiving a ‘This site can’t be reached. www.website.com took too long to respond. ERR_CONNECTION_TIMED_OUT‘ message.
I am not the web developer (for this particular website), simply an editor so any resources I can point our web developer to would be great. They don’t even want to accept that it might be the website and not the viewers setup (eg. computer/browser etc). They keep saying it’s the viewer’s browser. But in all my time as a web designer, I’ve never seen this issue before. One of our visitors says they just recently purchased a new Mac and the website still isn’t showing.
Things I have tried to do to rectify the issue:
…but people are still having issues
FYI – We have another website having the same issue but it’s Version 4.3.4.
Ian
]]>Please fix my RSS feed? Thank you.
]]>