right, any plans to update the plugin?
It seems to work with 2.9.2 except I’m having some weird jQuery issues on the WP admin pages. For example, if Great Real Estate is activated and you go to edit a Post or Page you cannot toggle any of the post boxes (Attributes, Custom Fields, etc). This pretty much renders the plugin useless until these bugs are squashed.
I think I fixed the issue. Simply replace the jQuery Validation plugin the is bundled with Great Real Estate with a more recent version:
http://ajax.microsoft.com/ajax/jquery.validate/1.7/jquery.validate.js
And everything should be working again. I need to do some more testing but so far this seems to do the trick.
The file to replace is here:
great-real-estate\js\jquery.validate.js
I am using plugin version 1.3.1 with WordPress 2.9.2, and I am also having issues. When I click “Create a Listing” I get the standard page form, but changing the Main Page to my listings page doesn’t give me any new fields or anything like that.
I have updated the jQuery plugin…is this a compatibility issue or am I missing something fundamental?
Thanks,
Ken
Please ignore that last post. The problem wasn’t the fields – those appeared below (the preview showed them in the ‘edit page’ box itself).
@mindshare, I’m updating that file in 1.4 which should be available on Extend any moment now. That and a few links seem to be the only issues for 3.0 (excepting any third party plugin changes, of course).
Thanks for pinpointing the issue.
@bamajr – the compatibility warning goes away when enough people chime in on Extend saying whether the plugin works. Also, given that 2.9 had no breaking issues, I didn’t update the readme.txt file, which is part of the warning logic apparently.
Anyway, @everyone – a new 1.4 release is out. Please report any issues here or in my forums. And if it works, please go to the plugin page and click “Works” for your config to help other users out.
Roger, this is not working for me. I can’t get to the listing page, it just takes me to the standard page entry form.
Ugh. Disregard. I figured it out. Once I saved the page the property info shows up. From a usability standpoint it’s a little confusing. But it works.
Ugh. Disregard. I figured it out. Once I saved the page the property info shows up. From a usability standpoint it’s a little confusing. But it works.
Thread Starter
bamajr
(@bamajr)
@roger Theriault – apparently there are two spots where the compatibility of a plug-in is identified. Also, any one who uses the “Better Plugin Compatibility Control” plug-in on their WordPress site will identify this issue.
Your readme.txt file shows:
Requires at least: 3.0
Tested up to: 3.0
If you have tested it this plug-in upto 3.0.1, it should read:
Requires at least: 3.0
Tested up to: 3.0.1
Just an observation: If this would have been done correctly, it may not have taken so long for the compatibility to update on the WordPress Plug-ins Directory.
Before you ask, I do know where to change this at, but it is a hassle. A bunch of plug-in developers seem to forget this one little spot.
