websitezcom

I found the issue. You must be using an older version of PHP. I had a piece of code that used something that was relatively recent for PHP.

Version 3.1.1 should fix this. It will be live momentarily on www.remarpro.com.

I found the issue. You must be using an older version of PHP. I had a piece of code that used something that was relatively recent for PHP.

Version 3.1.1 should fix this. It will be live momentarily on www.remarpro.com.

Let me know and I will close this out.

Can you turn on debugging?

Also, it may be necessary to edit this file “wp-mobile-detector/websitez-wp-mobile-detector.php”

At the top is this:

define(‘WEBSITEZ_MODE’, ‘production’);

Change it to:

define(‘WEBSITEZ_MODE’, ‘debug’);

This should then report the problem on the blank pages.

Would it be possible for you to turn on debugging and see what the error is?

In wp-config.php, you can turn on debugging with this:

define(‘WP_DEBUG’, true);

Is the menu empty, or it won’t open?

What does the “Menu” tab on the mobile theme settings page show if the menu is blank?

Which theme do you have selected?

Does the upgrade to PRO page or the What’s New page load?

This is likely caused by a corrupt installation.

I would de-activate, and uninstall the plugin. Then install it again so you can get the most recent files. There was an issue for a short period of time where not all of the plugin files were being downloaded.

Also, it needs the permissions fixed to work properly, which is why that notice is present.

Keep in mind that you may have version 3.1, but the current version 3.1 up on www.remarpro.com is different.

Can you send me a screenshot?

Also, just to confirm, it would be worthwhile to delete all plugin files, and redownload from www.remarpro.com.

Thank you, glad you like it!

Just for the plugin, or your entire administration area?

Sorry about that, appears to be an issue with SVN. It is not adding all of the files even though they have already been added.

Version 3.1 has this fixed.

This might have been related to the fact that I just pushed a new version live. The new version was being set live just as you reported issues. You can see now that instead of version 1.8, it is now version 3.0.

I agree, it is terrible. I apologize for the frustration. This has happened a few times in the past. This plugin has been around for years, and only a handful of people have had this issue.

Every time I looked into why it happened, it was caused by another plugin conflicting with mine.

You can easily look at how many versions of the plugin there have been, and how many support tickets related to this to see this is the case.

Unfortunately some plugins aren’t written correctly. I wish there was more I could tell you.

Anyone with any experience knows that this problem could be caused by another plugin that is written incorrectly.

Jumping to a conclusion is the only amateurish part of this.

Honestly…