tomdkat
Forum Replies Created
-
Ok, I disabled Autoptimize and resaved the WP Fastest Cache settings and NOW the pages aren’t always served via PHP. I also learned something about the DiVi theme. When I empty the WP Fastest Cache cache, the first time a page is viewed, the “DONOTCACHEPAGE” flag is set, by DiVi, to allow generation of the CSS files before the page can be cached. Then, if I view the page again, WP Fastest Cache creates the cached version. Then, if I view the page again, the cached version is served and now not via PHP all the time.
We installed Autoptimize to help with the previous theme and this new DiVi theme is so much faster, we probably don’t need Autoptimize anymore.
Thanks!Nevermind. I figured out the percentage is the percentage difference between yesterday’s traffic and the day prior to yesterday. 🙂
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Divi 5 breaks preloadSo, this is the description of the “Critical CSS” option in DiVi 5:
Critical CSS greatly improves website load times and Google PageSpeed scores by deferring non-critical styles and eliminating render-blocking CSS requests.
Is this still recommended to be disabled?Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Divi 5 breaks preloadI just converted a site to DiVi 5, so thanks for posting this information!
Forum: Plugins
In reply to: [Simple Login Log] Question about failed loginsHi! Thanks for the response! It’s been sooo long now, I forget the details of my change. I might have added a column to the failed login table to store the failed password or otherwise grabbed it from the same spot where the login log was getting the data it did store. Regardless, it I think it was being stored in plain text.
Your points about security and spot on, but there’s got to be a way to what the failed attempted passwords were. I mean WordPress rejected the password and there’s just no record of what that “bad” password was. Your point about the database being accessed by an unauthorized party is completely valid. If database access were actually achieved, they would have access to *all* the passwords and then we have a completely different problem to deal with. 🙂 lol
In any event, the only reason I mention this is because I noticed this plugin was recently updated and I had actually completely forgotten about it, until this update. In fact, when I saw it was updated, I was concerned that a “bad actor” had taken control of the plugin and well, you can imagine the rest. 🙂
Anyway, thanks for taking the time to reply. 🙂Ok, I’m logged into my dashboard now. When I go to ‘Statistics’ > ‘Optimization’ I don’t see “Purging” but I see:
Overview & Info
Data Export
Data Cleanup
Plugin Maintenance
Historical Data
I can see the overview info fine and it shows the amount of PHP memory being used, etc. When I click the other items, nothing happens. Are those premium features? If so, I’ll try the table deletion again and I’ll verify everything got deleted as expected.Thanks!
Hi! Thanks for the great response!!!! So, if I use the “Purging” section to purge the data, should I expect all of the counts to reset to 0? I do use a caching plugin (WP Fastest Cache) but I believe I emptied the cache after removing the plugin, such that when I re-installed it, it would install correctly (not having cached data interfering).
Thanks!Sorry for the delayed response and thanks for the info! Believe it or not, the attack HAS NOT STOPPED since I started this thread! I do have the latest/current version of the plugin so I’m not as worried/concerned.
Thanks again!
Forum: Themes and Templates
In reply to: [Twenty Ten] Theme version 3.4 update causes blog to crashSo far, the “stub” block-patterns.php file appears to be working ok, with version 3.4 of the Twenty Ten theme.
Thanks for the reply! We were running PHP 7.4.11. I have since upgraded our hosting space to use PHP 8 and the issue has been resolved.
Thanks!
*sigh* Sorry for the typo in the post title. I guess I can’t type today. 🙂
Wow, this IS weird. So, when I try to update from the WordPress update page, the update doesn’t work. However, I just went to the plugins page and used the “Update now” link and the update worked. The ONLY thing I can think of is I had the site in “maintenance mode”, using the “Maintenance” plugin. I took the site out of maintenance mode before doing the upgrade.
Anyway, I’m upgraded now so I’m happy.
Thanks!
Peace…
Forum: Plugins
In reply to: [Maintenance] Background image doesn’t appear in Maintenance mode@528491-1 Thanks again for the “lazy loading” tip. I setup Autoptimize to exclude the background images from “lazy loading” and now they load just fine.
Thanks again!
Peace…
Forum: Plugins
In reply to: [Maintenance] Background image doesn’t appear in Maintenance modeThanks for the info! I ended up excluding the background images from lazy loading and that did the trick.
Peace…