Maxim Peshkov

Hello @rishi2411. Please, note, the fatal error you experienced ‘Can’t use function return value in write context‘, belongs to PHP 5.5 and less.

Prior to PHP 5.5, empty() only supports variables; anything else will result in a parse error. In other words, the following will not work: empty(trim($name)). Instead, use trim($name) == false.

More details ishere

In general, it means, that the version of PHP on your server is too old. And, you may face with a bunch of other Fatal Errors, even if the current Fatal Error will be fixed.

WP-Stateless plugin ( and most of other ones ) support PHP 5.6 and higher.

Anyway, the Fatal Error is fixed and it will be available in new ‘hotfix’ release 2.0.2 shortly. Until, new WP-Stateless 2.0.2 is not launched, you can download the plugin with fix here.

Regards

Yep, I just did some tests. I believe, the issue is solved now. Thank you!

To solve the issue with Gmail SMTP plugin, we added back compatibility with Google SDK 1.x. to our WP-Stateless plugin. But, suddenly you launched new version of plugin which contains cut version of latest Google SDK. And… it just broke our plugin again….

Please, look through my comment here.

you should not load Google SDK on every page load ( on plugin initialization ). In other case, you will face with another conflicts: when other third-party plugins are using legacy Google SDK ( < v2.0 ).

It also belongs to other Google SDK versions, since you’re using cut version of SDK…. And, even more fact, Google SDK 2.0.0 has conflicts with Google SDK 2.2.0… So, I’m absolutely sure you will get much more support topics now, regarding conflicts with other plugins which also use Google SDK.

I believe, that the problem is not a version of Google SDK, but how you’re initializing it. To prevent the most potential issues with other plugins, you just needed to start loading your Google SDK ONLY when it’s really needed, but not on every plugin’s initialization…

Regards.

• This reply was modified 7 years, 3 months ago by Maxim Peshkov.

To solve the issue with Gmail SMTP plugin, we added back compatibility with Google SDK 1.x. to our WP-Stateless plugin. But, suddenly you launched new version of plugin which contains cut version of latest Google SDK. And… it just broke our plugin again….

Please, look through my comment above.

you should not load Google SDK on every page load ( on plugin initialization ). In other case, you will face with another conflicts: when other third-party plugins are using legacy Google SDK ( < v2.0 ).

It also belongs to other Google SDK versions, since you’re using cut version of SDK…. And, even more fact, Google SDK 2.0.0 has conflicts with Google SDK 2.2.0… So, I’m absolutely sure you will get much more support topics now, regarding conflicts with other plugins which also use Google SDK.

I believe, that the problem is not a version of Google SDK, but how you’re initializing it. To prevent the most potential issues with other plugins, you just needed to start loading your Google SDK ONLY when it’s really needed, but not on every plugin’s initialization…

Regards.

• This reply was modified 7 years, 3 months ago by Maxim Peshkov.
• This reply was modified 7 years, 3 months ago by Maxim Peshkov.

Hello,

To prevent the issues with other plugins, which are using Google SDK, you should not load Google SDK on every page load ( on plugin initialization ). In other case, you will face with another conflicts: when other third-party plugins are using legacy Google SDK ( < v2.0 ).

Hello,

The bug belonged to WP-Property 1.35.0 and older versions.
It’s also mentioned in provided article.

Regards.

Hello,

Please, look through the related topic here.

Also, please, ask your host provider about your PHP version. I think, you may be wrong about current one.

[26-Dec-2015 06:09:59] PHP Parse error: syntax error, unexpected T_STRING in /home8/landmav4/public_html/testlandmark/wp-content/plugins/wp-property/wp-property.php on line 54

The error, you mentioned, must not occur on PHP 5.3 and higher.

Regards.

Hello,

As I understand, you have fatal error on trying to install/activate WP-Property 2.x.x which causes 500 Error. To see the error you should enable debug mode. See doc here.

define('WP_DEBUG', true);

And, be sure, that the errors are being displayed.

define('WP_DEBUG_DISPLAY', false);

Please, let us know, which error occurs on WP-Property 2.x.x activation.

Regards.

The site is now on PHP 5.6. After I made the switch I upgraded to the latest WP Property- white screen of death.

As I understand your current PHP version is 5.6 now, but some Error still occurs. Which exactly Error do you have now? If you still are having the same errors as before, so your version still is not 5.6.

So I went back to the 1.42.0 version (the only version that doesn’t cause white screen of death) and now I’m back at the starting place, no properties showing on the admin panel.

I already mentioned about WP-Property 1.42.1 and lower versions incompatibility with WordPress 4.3 and higher ( see my post above ). What is preventing you from using WP-Property 1.42.4 (the latest stable version of WP-Property before 2.x) ? I believe it should solve the issue with not showing properties on ‘All Properties’ page, in case you do not have success with installing and activating WP-Property 2.x version.

See screen: https://screencast.com/t/gS5EtOPX

Regards.

The error is occurring because of using namespaces in code.
Screen : https://screencast.com/t/cJCtJrOgCd

I saw, you mentioned that your current PHP is 5.6. But, I think, you may be wrong.

See the error occurring on many PHP versions.

Also, look through related topic here.

Regards.

Hello,

Regarding your current WP-Property version.

currently using 1.42.0 and I still can’t access my properties from the admin panel.

Maria mentioned that WP-Property 1.42.1 ( actually, 1.42.2 and less ) is not compatible with the latest WordPress versions ( 4.3 and higher ). It’s the reason, why any property is not shown on All Properties page.

As I understand, you have fatal error on trying to activate WP-Property 2.x.x. To see the error you should enable debug mode. See doc here

define('WP_DEBUG', true);

And, be sure, that the errors are being displayed.

define('WP_DEBUG_DISPLAY', false);

Please, let us know, which error occurs on WP-Property 2.x.x activation.

Regards.

Hello,

Numeric Sorting only works for attributes which have ‘numeric’ or ‘currency’ Data Entry.
You can manage your attributes ( including Data Entry ) on Developer Tab on Settings page.
Also, be sure that you have only numbers or float values for particular attribute.

Regards.

how do I set the search up for specific amounts like between 50,000 and 100,000 (and so on)

You should set Advanced Range Dropdown with your custom values for Search Input on Developer Tab ( Settigns page ).

Example: https://screencast.com/t/rWCxwPpQ

Regards.

Hello,

Make sure, that you set ‘Currency’ Data Entry for your price attribute on Developer Tab (Settings page), but not ‘Numeric’.

Regards.

Make sure, that you set ‘Currency’ Data Entry for your price attribute on Developer Tab (Settings page), but not ‘Numeric’.