Desktop not detected simulating a desktop device

Hi @gilles24

thank you for reporting this issue.

This is a new feature for self-debugging. When you save a post or page, SCFM checks if the page is not served by the same cache both on mobile and desktop.
It’s very important to check it because it’s the most frequent cause of issues.

However, looking at your page it looks all ok, so I think this is a false issue detection.

I will try to reproduce the same issue and solve this problem. Until the bug is solved I suggest ignoring this message.

You can try to save a page in the backend, and if the message doesn’t go away, I suggest you, wait for the next release. If all was working before the last update, you don’t have to worry about this message. Probably something doesn’t work as expected during the check.

Thank you for your reply.
I confirm that the message appears and doesn’t go away each time I save a page.
So I’m waiting for the next update.
Regards,
Gilles

Hi @gilles24

I was able to reproduce the same issue on my installation.
Please, follow these steps:
– update to version 0.1.8.6
– refresh the page where you see the warning, no matter which page, whatever page of the backend where you see the warning is ok
– dismiss the warning
– save a mobile version page
– check if you see again the same warning

Please, let me know if you still see the same false issue detection after following the suggestions abovve.

I did exactly as you recommended. But the warning still appears.

On the other hand, it no longer appears on pages without mobile versions (whereas it was the case before).

Hi @gilles24

are you sure is still a false detection. I’ve checked again the debugging and for me, it works.

Is it exactly the same message as before?

Would it be possible to share the URL of the page?

Hi Jose,

Yes, it’s the exact same message.
And it is indeed a false detection (it is indeed the mobile version that is displayed on my mobile).
See for example this page: https://www.un-jardin-bio.com/ebooks/mon-potager-au-naturel/

I don’t know if this is related, or if it can help you, but I have this warning (repeatedly) in the error_log file
PHP Warning: Undefined variable $actual_desktop_id in /…/wp-content/plugins/specific-content-for-mobile/admin/scfm-admin.php on line 436

Hi @gilles24

The new version 0.1.8.7 fixes that warning. I suggest you update.
However, I’m not sure it will also fix the false issue detection.

Let me know. If after the update you still have the same issue detection I will provide you with a version of the plugin that adds to the debug.log file useful information to understand what is going on.

The same message always appears after updating…

If the warning is still related to line 436, it is theoretically not possible with version 0.1.8.7

What’s the PHP vesion that runs on your server?
You can check it in Tools => Site Health => Info => Server

The warning now only appears on the mobile page when I update it.
But there is no more error displayed in the error_log file
I have PHP 8.0.13 version

Hi @gilles24

ok, I confused the PHP warning with the message in the backend. I meant the PHP warning was not possible.
Now we will investigate the message in the backend.
I will provide soon a version of the plugin to write information in the debug.log.
I think in 1-2 days. Until then, ignore that message because as I understand your site is working well.

Hi Jose,
Non solution ?

Hi Gilles,

sorry, it took much longer than I thought.

I suggest you:

– Update to the new version 0.1.9.0
– Check if you still have the same problem

If you still have the same false detection:

– Install and activate this plugin: https://plugins.svn.www.ads-software.com/specific-content-for-mobile/branches/debug-scfm-warning.zip
– Enable the debugging in wp-config.php by adding these lines before the comment /* That’s all, stop editing! Happy publishing. */:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

– Try to save a gain a mobile version, or a page that has a mobile version
– Check the file wp-content/debug.log, and please, let me know what you find
– After copying the content of debug.log disable the debugging by removing the lines of code above, or setting false WP_DEBUG. In another case, you risk that that file becomes bigger and bigger.
– After the debugging, you can remove the plugin Debug SCFM Warning. This little plugin will work only with the last version of SCFM.

In any case, you can deactivate the warning by adding this line of code in wp-config.php before the comment /* That’s all, stop editing! Happy publishing. */::

defined( ‘SCFM_DEBUG_NOTICE’,false );

Or, by adding this line of code in the functions.php of your child theme if any, or in a functional plugin:

add_filter( 'scfm_debug_notice','__return_true' );

Have a great day!

Jose