machouinard

Upon further debugging, it seems the plugin was using the profile_id of a deleted set of RETS credentials.

Actually there’s a ton of leftover stuff in the database after deleting the connection. I would not have thought deleting a connection would leave behind so much.

I realize the RETS stuff is more advanced and client needs to purchase support. Feel free to ignore the above comments as I’m unable to delete them.

The previous error appears whenever cron runs the es_mls_schedule_hook.

We switched to a real cron job and, unsurprisingly, here is the output:

--2020-09-19 21:50:01--  URL/wp-cron.php?doing_wp_cron
Resolving URL (URL)... #.#.#.#
Connecting to URL (URL)#.#.#.#:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2020-09-19 21:50:01 ERROR 500: Internal Server Error.

• This reply was modified 4 years, 1 month ago by machouinard. Reason: add detail

PHP Fatal error: Uncaught Error: Call to a member function build_query_string() on null in PATH/wp-content/plugins/estatik-premium/mls/classes/schedules/class-mls-import-schedule.php:107

Auto import is occasionally working on local dev site. Still not working on staging.

We have a single set of MLS Credentials using RETS, connecting through Bridge Interactive. We are receiving data and have been able to configure fields.

For what it’s worth, we have 230 fields mapped to MLS values.

Even with things like beds and baths, people make mistakes and need to update the MLS with corrections. Those corrections could affect almost any of our 230 fields.

On the other hand, we have a single field we’d like to make sure does not get updated during sync.

• This reply was modified 4 years, 1 month ago by machouinard. Reason: fix typo
• This reply was modified 4 years, 1 month ago by machouinard. Reason: fix typo

Looking forward to it.

Thanks @gvectorssupportmember

Thank you Ben!

Mark

For @maaronslc and anyone else regarding the GhostPool theme, this has been fixed in version 2.39.1 of the theme.

Like @maaronslc I have a client using Socialize by GhostPool. Client’s support has expired and the author has drastically increased renewal costs in an effort to deter new customers – not verbatim but that’s his intent.

We’re currently stuck on TEC v5.0.3.2. Any version after that, the Venue and Organizer options are “missing” when editing Events.

In our case, it looks like it has something to do with $container.data( 'select2' ) being null on line 411 of /common/src/resources/js/dropdown.js. This appears to be dealing with the timezone field – the field just prior to Vendor and Organizer.

I’ll post here if we find a solution. Please do the same!

Hi, Adam.

Apologies for the delay. I’ll have to look into why I wasn’t notified of your post.

For future reference, all support is best handled at GitHub.

The latest version (0.5.0) takes care of this issue as well as some possible problems when using CDN.

Thanks for the kind words and please feel free to contact me via GitHub if you have further questions!

@markzahra

We’re using a custom plugin for various things on this site with a JS file already enqueued. As a temporary solution I simply added a function with the above code and am calling it on $(document).ready and ajaxComplete.

I’ll provide settings/feed detail and screenshot when I’m back at my desk. Theme in use is Socialize from Themeforest. Open links behaviour is set to open in new tab.

Looks like it should be under Link Preferences => Open links behaviour in the template but it’s not working for me.

Temporary workaround:

I had to add the ‘target’ attribute with some JS.

document.querySelectorAll( 'li.wpra-item.feed-item a' ).forEach( function( link ) {
			link.target = "_blank";
		} );

• This reply was modified 5 years, 4 months ago by machouinard.

Was looking for the same tonight. In case you still need it-

https://www.ads-software.com/support/topic/make-fixed-widget-stop-at-footer?replies=12

Events Calendar just pushed a 4.0.1 release. Seems to have fixed this for me.

Look in wp-config.php for define('WP_CACHE', true); and remove it or comment it out. Sounds like you may have been using a caching plugin without copying advanced-cache.php into wp-content.

Marking this as resolved. Latest version of plugin incorporates the changes necessary to fix this issue.