craigmische

I am continuing to use the plugin for now. The reason is my MLS is making a change next year so as I already paid Realtyna it doesn’t make sense for me to make a change to a different provider right now as I will have to start from scratch early next year after my MLS joins a larger MLS. Here are the pros and cons as I see them and why I changed to my rating to 3 stars.

Pros:
1) An employee named Mark. He has been a good partner.
2) The plugin can produce an aesthetically pleasing display of listings.
3) If functioning properly, the cost is appealing if you plan to use WPL long term.

Cons:
1) Trust. I have found I can’t depend on the setup of the plugin. The most recent example is I found that query fields required to have listings imported that are commercial, multifamily or farmland was incorrect. No new listings had been imported for a few months. The query identified for those 3 categories was the residential identifier.
2) Development speed. Because of Mark, I’d consider staying with WPL but it took 3 months to get up and running the first time and I won’t even likely have 2 weeks this time around. The person from Realtyna that commented on my change to 3 stars will likely state that the reason it took so long were my requests for changes but that was because a) there were a lot of needed changes and b) the turn around time was typically 24 hrs no matter how basic the request.
3) Photos. Web-site speed is important regardless of the product. When WPL imports photos, it resizes them but only after the initial viewing of a listing by any user. The result is the first view of a listing will take anywhere from 15-45 seconds or not load at all resulting in a timeout error. I inquired about it more than once and was finally told there was a workaround but it’d cost $200.

Before I respond, what brokerage or agent site are you working on?

Thank you. The error message in the console is:
Uncaught TypeError: Cannot read property ‘secret’ of null
at a.wp.receiveEmbedMessage (wp-embed.min.js?ver=4.9.8:1)

One work around I found is I can disable AWB, start the customizer and then quickly enable AWB again and the customizer will still work.

Thank you Keith!