Update breaks plugin

Yes, the update breaks the plugin. Please fix and thank you. It’s an tremendously terrific plugin and we appreciate that you created it and maintain it. Thank you ??

I saw in another post area that upgrading the php on the server will do the fix, and it does. I upgraded to 5.4. Thank you.

I followed the instructions from my hosting and upgraded to 5.4 with no luck, I get the same situation as I mentioned previously

Hello, solutionstriware.ca

We need more info about your issue in order to help you.
Did you try to switch theme and disable third party plugins?

Regards.

I was looking into the plugin and the reason the plain-text occurred, was due to updating the plugin, which dropped the files relating to the premium features. The premium feature in question, being “real estate agents”, which filters listings by agent and allows for agent profiles. Even after clicking the “Check Updates” button on the site under the Settings/Main page, it wasn’t re-added, though I did have the latest version (the admin feature was the only feature re-added)

To sum up, the update wasn’t the cause for functionality to be broken however, pagination and agent filtering is still an issue. Code-wise, the Query string that’s created by accessing another page via pagination causes this link https://triwarebeta.ca/coldwell/agent-listings/?agent_id=51 to go to https://triwarebeta.ca/coldwell/agent-listings/?agent_id=51#/requested_page=2&sort_order=DESC&sort_by=menu_order&i=1, in which case I noticed that the query string was ignored and the filter returned 0 data matches for an agent (but still the total listings associated with that agent)

Hopefully this is more than enough info to get a better handle of my situation. The link is below for our Agents page:
https://triwarebeta.ca/coldwell/agents/

Actually yes, when I was testing it returns on second page – “Sorry, no properties found, try to expand your search”

Is this what are you talking about?

Regards.

Turns out, we had generated a custom solution to combat this situation and have reverted to our previous code. Sorry for the confusion, my other posts will be marked as resolved also.

I didn’t get a chance to see your post 40 minutes ago, but yes, that was exactly the case I had and the complaint we had from our client.

Ok. Thank you for pointing, I have also found this issue. This will be fixed as soon as possible.

Regards.

The custom edit we made was around line 1555 to 1605 of the latest core\class_core.php file in the plugin. I know it took me a long enough time to find where the issue was, hope this helps with the fix on your end.

Cheers.

Hope update plugin is coming soon.

For quick solution, I’ve updated the core file
/wp-content/plugins/wp-property/core/class_core.php

In function admin_menu()
=========================
` $all_properties = add_submenu_page( ‘edit.php?post_type=property’, $wp_properties[ ‘labels’ ][ ‘all_items’ ], $wp_properties[ ‘labels’ ][ ‘all_items’ ], ‘edit_wpp_properties’, ‘all_properties’, function () {
global $wp_properties, $screen_layout_columns;
include “ui/page_all_properties.php”;
} );`

REPLACED CODE

$all_properties = add_submenu_page( 'edit.php?post_type=property', $wp_properties[ 'labels' ][ 'all_items' ], $wp_properties[ 'labels' ][ 'all_items' ], 'edit_wpp_properties', 'all_properties', create_function( '', 'global $wp_properties, $screen_layout_columns; include "ui/page_all_properties.php";' ) );

And in function add_settings_page()
====================================
`$settings_page = add_submenu_page( ‘edit.php?post_type=property’, __( ‘Settings’, ‘wpp’ ), __( ‘Settings’, ‘wpp’ ), ‘manage_wpp_settings’, ‘property_settings’, function () {
global $wp_properties;
include “ui/page_settings.php”;
} );`

REPLACED CODE

$settings_page = add_submenu_page( 'edit.php?post_type=property', __( 'Settings', 'wpp' ), __( 'Settings', 'wpp' ), 'manage_wpp_settings', 'property_settings', create_function( '', 'global $wp_properties; include "ui/page_settings.php";' ) );

And now looks good to my site in updated version and latest plugin.

Hope this helps on your end also.

Thanks