adfisch

Hi @stevejburge,

I just updated from WP version 6.1.4 to 6.2.4 and the box re-appeared. I guess this means your new plugin version is not compatible with the old WP version?

Thank you!

Sorry, I just updated the post before:

So far we have completely reinstalled the plugin without success. Also, our system used to work with real cron jobs (so we had WP Cron deactivated). We switched back to WP Cron, also without success. Do you have any more recommendations on further steps?

Hi there,

we actually have the same issue (find screenshot attached) and where just about to post when I saw this thread. Your plugin used to work fine until recently, now other system settings have changed in our ecosystem. Could it be, that there came some kind of bug with the latest update?

Steps taken so far: Deactivation and complete re-installation of the plugin without success.

Thank you!

• This reply was modified 1 year, 2 months ago by adfisch.

Hi @wpmudevsupport11,

thank you for your reply. I made a few adaptions and now everything works perfectly.

Thank you for your help! ??

Hi @wpmudev-support8 and @wpmudevsupport11,

thank you for your fast replies. I have one last question and would appreciate your help: Since there is no ETA on the ability to disable the default article markup, is there a way to programatically remove it?

I know that I could deactivate the Schema module. However, this also prevents me from using the Schema Builder or Breadcrumb Feature. Thus, a code snippet for only disabling the article schema would be very handy.

Thanks a lot.

Hi Adam,

thank your for your code snippet. It worked perfectly! ??

Adrian

Hi Zafer,

thanks for your fast reply. Yes, I have installed SmartCrawl 3.6.5. You should be able to replicate the issue by:

1. Making sure that you have a static page as your home page.
2. Activate the Breadcrumb feature in SmartCrawl > Advanced Settings.
3. Under “Configuration” set “Add homepage to the breadcrumbs trail” to true and provide a label (in my case “Startseite” which is German for “Homepage”).
4. Now, evaluate the Breadcrumb Schema markup, e. g. with Google’s Rich Results Test Tool. Since we are on the front page, there should only be 1 breadcrumb. However, even the homepage gets itself added to the trail. So there are 2 breadcrumbs of the homepage instead of just one (see my screenshot above).

Possible and easy solution: When prepending the homepage to the trail in your code, add the following conditional statement:

if ( ! is_front_page() ) { ... }

Thanks for your help. I am looking forward to your reply. ??

Hi Luis,

thank your for your fast reply and forwarding the idea. In the meantime, is there a way to programatically disable the SmartCrawl box for certain post types? I just realized I only have the code snippet to disable it for certain taxonomies (https://www.ads-software.com/support/topic/disable-smartcrawl-for-certain-taxonomies/).

Thank you so much in advance.

Hi @vmarko,

since you haven’t replied, yet, I thought the solution cannot be as easy as I anticipated. Thus, I had a further look into this and wanted to contribute what I found out.

In order for W3TC to work with ES6 modules, it would need the following updates:

A) Modules will likely not work with all JS minifiers/compressors. I found that Terser works perfectly when using the setting module: true. So either Terser needs to be added to the compressor list or the other compressors need to be examined for their ES6 module support.

B) Modules (by their nature) cannot be combined, so they must be excluded from combine automatically.

C) For modules to be recognized as such by the browser, the script attribute “type” must be preserved when inserting the minified script: <script type="module" src="path/to/minified/file.js">.

I hope this idea finds its way to the developers since this would greatly enhance W3TC. I would appreciate an answer if this feature will ever be introduced and – if yes – what the estimated timeline is. If you need any assistance, I would love to help.

Thanks for your reply!

Hi @shanedelierrr,

thank you for your fast and competent feedback.

Concerning the deprecated messages: I have done some more research on these messages after realizing some of them will even be displayed when using PHP 7.4. Deprecated messages mean that your codes uses a functionality that will be removed in the future, however, is not considered an error with the current PHP version. With this background information I expected your developers might not fix the messages in the near future (which is understandable). Thus, we had some intense discussion with the hosting company and they finally managed to hide deprecated errors.

In sum, the problem seems to be solved on our side. However, the information might still be helpful for your developers in the long run.

Creating users with weak passwords: I used the admin interface for managing users and ticked the “Confirm use of weak password” box. I was expecting this function not to work anymore.

Replication of error messages: The deprecated warnings occured since she set up the email 2FA (unfortunately, she cannot remember the exact stage). After that, the warnings will appear when she accesses the login page event before attempting to login. I could not replicate the warning myself but have copied them off screenshots, so they actually appeared.

Again, thank you for your great help. I will mark this thread as closed since the problem is solved on our side. I hope, the discussion was still helpful to you. ??

Thanks for your fast reply. As requested:

• PHP-Version: The warnings occur for 8.0, 8.1 and 8.2 (we tested all), it seems to work with PHP 7.4
• WordPress-Version: 6.1.1
• Plugin-Version: 8.1.4

We are looking forward to your reply!

Short update: So the (stupid) hosting company my customer is with allows only directory-based changes to the PHP settings making it impossible to hide error messages.

I would really appreciate if one of the developers could look into this as the errors definitely occur as of PHP 8.0 and PHP 7.4 has already reached end of life. So PHP 8.0 compatibility should be a must-have, right? ??

Thank you very much in advance.

Hi @nlpro,

thank you for your reply.

I already rolled back to PHP 8.0 but the notices still appear. So I guess there’s still some work to be done in order to be fully PHP8-ready.

You’re right, the fact that the messages appear got me a little bit confused since I have WP_DEBUG set to false and error_reporting(0);. Seems the server must overwrite the settings somehow. I will check.

Thanks.

Hi @ironikus,

thank you very much for your fast reply. Just out of curiosity (I understand you develop this plugin in your free time – so no hustle): Is there a timeline for the next release? Thanks for your answer! ??

Hi @vmarko,

just checking if you have any news on this? ??

Thank you!