yallaman

Strange. Two weeks ago another user had the same problem:
https://www.ads-software.com/support/topic/full-cache-delete-on-post-edit/

The issue was not resolved (because he moved on to another caching plugin). Hopefully the plugin author can chime in.

Did the problem start with the update last week (version 1.12.0)?

I have used this plugin for many years, and I have never experienced that all cache is deleted when saving a draft. I was thinking of updating to 1.12.0 today, but I will wait until we hear from the plugin author.

Edit:
Do you, by any chance, have “Clear all cache files when a post or page is published or updated” enabled in the Advanced tab in the plugin settings? I have it disabled/off.

• This reply was modified 1 year ago by yallaman.

Small update:

1. When activating the preload process manually using the button, the preload notification panel starts listing the four first preloads. Then the panel stops updating. However, the plugin is still preloading my pages and posts, which is good.
2. After preload finishes – which I carefully check using FileZilla – the preload notification panel still says it’s active.
3. In addition, preload is now roughly three times slower than before (i.e. prior to version 1.10.0). I have around 130 posts/pages/tags, and I know approximately how long the preload process has taken in the past.

FYI: Since I started using this plugin a few years ago, “preload_permalink.txt” has always been present. It has not caused any problems (until after I updated to 1.10.0).

Every month I manually delete the cache and initiate preloading. Previously, there was no notification panel, so I used FileZilla to check that my pages/posts were cached and that preloading had finished. The “preload_permalink.txt” file changed during each preload process, but it was always there.

Also now, after sucessfully running preload in 1.10.0, the “preload_permalink.txt” file is still there. And since the “Preload Cache Now” button is back, it appears the file is not causing any issues.

In wp-content/cache/, the file “preload_permalink.txt” was present, but not “preload_mutex.tmp”.

I followed your suggestion and deleted “preload_permalink.txt” using my FileZilla FTP client. After logging out and in again, the “Preload Cache Now” was back. After initiating preload, I could see that the preload process was active via the new preload notification panel. Nice!

Preload seems to be working as it should. Thank you for your help!

PS: I don’t quite understand the last part of your message, regarding running a special command in a PHP file in mu-plugins etc. etc. Since manually deleting “preload_permalink.txt” seems to have resolved the issue, I assume I don’t have to implement the additional steps you mentioned?

As mentioned in my original post, I do see both the “Save Settings” and “Cancel Cache Preload” buttons. Only the “Preload Cache Now” button is missing.

I have now checked the source code carefully, and there is no “Preload Cache Now” text.

Hi @amirzia. Are you part of the development team?

You wrote that there is a conflict with Hueman and PHP 8. That is important information that users should have been informed about. (According to people here in the forum, there are also a couple of issues when using one of the more recent versions of WordPress.)

Do you know if the bugs and incompatibilities will be fixed and addressed in an update to Hueman in the near future? If so, it would make a lot of Hueman users very happy.

Since there are 1) no updates, 2) zero support (since 2022), and 3) no replies when contacting the developer, the Hueman theme is effectively dead as of now. Maybe it will be updated some time in the future, maybe not. Since 2022 Hueman has been in limbo.

There have been several WordPress and PHP version updates since the previous theme update. Hueman has not been officially tested with either of these.

People in the forum are reporting various issues with Hueman and the newer WP versions and PHP 8.x, so I’m still running older versions of both WP and PHP on my site. Maybe the issues are related to Hueman, maybe not. I don’t know. In any case, I need to update soon for security reasons. Fingers crossed, I guess…

I have used Hueman since early 2014 and also helped troubleshoot and fix a few bugs. I really like it, and I hope that the theme author will update/resurrect it and keep it alive.

Has anyone received any replies or status updates from the theme author? Wondering if the theme is abandoned or not …

In the theme options menu:

First select Main Body Design, then Single Posts Settings.

Directly under RELATED POSTS there is a small heading called Single – Related Posts. Select Disable.

Thank you very much for your replies. I have updated the plugin, but unfortunately the issue with the wrong name and wrong URL in the schema markup for pages remains.

The data in the first “ListItem” line looks fine:

{"@type":"ListItem","position":1,"name":"Home","item":"https://www.example.com/"}

It’s the second “ListItem” line on my pages that contains the wrong name and URL:

{"@type":"ListItem","position":2,"name":"Diverse","item":"https://www.example.com/category/diverse/"}

I have not made any changes to the WP code or theme code regarding queries or other things.

I have provided further details to you via the contact form on your website. Hope you get my message.

I use only two plugins on my website: Slim SEO and WP Super Cache. (I have never used any other plugins, because I have always tried to keep my site fast and light-weight.)

I have not set category taxonomy to my pages (I did not even know it was possible).

Thank you very much for your quick reply and the explanation.

Regarding header cleaning: Yeah, I already have some code in my functions.php file that removes unnecessary information, disables Gutenberg and emojis etc.

By the way, I might also install your eRocket plugin since I would like to add social sharing buttons (I don’t need the other features) to my posts and pages. Seems like a simple and light-weight solution. I hope you will keep maintaining eRocket as well.

Anyway, thanks again. Case closed ??

I share your concern. The lack of both updates and support since the end of 2021 could, of course, be due to problems (personal or work-related) that the developer is facing.

Prior to December 2021 the theme was frequently updated. Then followed an unusually long period (6 months) with no updates and little support. Hueman was finally updated with much-needed bug fixes in the summer of 2022. Since then no updates and very little/no support. There is a large number of support threads and questions that have not been addressed at all, especially in the last year.

BTW: The officially recommended plugin to Hueman, i.e. Hueman Addons, has been removed by WordPress. The notice says: This plugin has been closed as of December 28, 2022 and is not available for download.

I hope the developer is ok and will find time to check the support forum and also issue updates to the Hueman theme. I have used it since 2014 and I like it a lot.

• This reply was modified 2 years, 1 month ago by yallaman.

Thanks for your reply, @mikemayhem3030.

Yes, after hitting the “Preload Cache Now” button, I wait until the preload process has finished before I do anything else in WordPress (it takes about 15 minutes). However, there is nothing to watch when doing this…

I have always done it this way, both before and after 1.9.0, because I don’t know if the process will continue “in the background” if I move away from the “Preload” tab. I use FileZilla (FTP client) to check when the preload process is done.

• This reply was modified 2 years, 5 months ago by yallaman.