Conflict with WP Types Views plug-in

Thanks for your report and for posting a link to the vendor’s site.

WP Types Views is part of a premium plugin. I hope you understand that I cannot afford to purchase premium plugins simply to provide support for MLA.

I have worked with the vendor on one of their other products (WPML) and I will contact them about getting a copy of WP Types Views to investigate your issue. I will leave this topic unresolved and post an update when I have progress to report.

Thanks for your understanding, your patience and your interest in MLA.

Hi David,

yes, I thoroughly understand. I posted a comment to my support ticket with them to see if:

A. They could give you a license
B. I could add your test domain onto my account

I also referenced this thread.

David,

here’s the reply I got back from the company

“… you may contact us (or the Plugins developer) via the email [email protected], elaborate on the issue and requests, and then we will be happy to help however it’s possible.”

Thanks.

Thanks for your updates. I haven’t received a reply to my initial query, so I sent another email to the address they gave you. I will update this topic when I have progress to report.

I am happy to report that the Toolset vendor has granted me access to their site and I have downloaded the components I need to investigate this issue. I will post an update when I know more.

Thanks for your patience while I began my investigation. I have set up a test site and installed:

• Media Library Assistant 2.31
• Toolset Types v2.1
• Toolset Views v2.1

I created a custom post type, a content template and a view. I found no problems with the post type and content template when MLA was active. I was able to use the MLA Media Manager Enhancements with the “Media” button on both.

The View editor gave me some trouble. On my system it takes about 12 seconds to load because of a “long running script” in my browser (Internet Explorer). Once it was loaded I was able to use the “Loop Output Editor” to add fields to the view without further problems. The “Loop Wizard”, “Fields and Views” and “Content Template” buttons work fine.

The View editor “Media” button did not work on my system. The modal window popped up but after a long pause it reported “No items found.” even though the Media library contains several images. When MLA is not active the popup makes two “query-attachments” Ajax calls. The first call returns all of the items in the Media Library, but is apparently ignored. The second call requests all items “attached” to the View and returns zero items; this is the call that causes “No items found.”

When MLA is active the results are similar, but the pause is much longer and for some reason 125 “query-attachments” Ajax calls are made before returning “No items found.” This is probably some bug caused by MLA or the combination of MLA and WP Views. I will work on that.

I am not able to reproduce the symptoms you report in your first post. Any additional details on the steps you take to cause the problem would be very helpful.

In the interim you may be able to avoid the problem without deactivating MLA entirely. Go to the Settings/Media Library Assistant General tab and scroll down to the “Media Manager/Media Grid Enhancements” section. Uncheck the “Enable Media Grid Enhancements ” and “Enable Media Manager Enhancements ” boxes, then scroll to the bottom of the page and click “Save Changes” to record your settings. That should remove all of the MLA scripts from the Toolset/Edit View screen and give you a better result. Let me know if that works for you.

Thanks again for your patience.

Thanks very much for your analysis. I’m also glad the Types/Views people helped out. It’s very much appreciated …even more so as you’re a free plug-in.

Tomorrow, I’ll try your work around and see how it goes. If it doesn’t work, I have no problem giving you access to the staging site. If there are any additional plugins I can install to help resolve this issue, just let me know. Happy to assist.

David,

the workaround worked. I disabled the 2 options you mentioned and I was then able to insert my field into the template.

I’m going to mark this as resolved.

Thanks for your analysis and persistence on this. Much appreciated.

Thanks for your update and the good news about the workaround. Thanks as well for your positive MLA review. Reviews and positive feedback are great incentives to keep working on the plugin and supporting its users.

I will work to resolve the conflicts between MLA and Toolset components. I will update and resolve this topic when I have a complete solution.

First, I must add my thanks to an author of a free plugin going the distance to debug a 3rd-party conflict!

Toolset is one of the most used plugins (at least for me, indispensable) so it’s great to get these two working together.

Not sure if it helps, but the error in my case (with both plugins on default settings)

PHP Fatal error: Class 'MLAData' not found in [...]/wp-content/plugins/media-library-assistant/includes/class-mla-media-modal.php on line 596, referer: https://[...]/wp-admin/admin.php?page=views-editor&view_id=86

Similar error on editing Page type posts using the WYSIWYG editor when trying to bring up a modal from Views/Types. It looks like the Ajax request is triggering something MLA has hooked but isn’t present.

Thanks for your patience while I cleared my backlog and got time to work on these issues. I have done some further testing on my on system and aside from the “Media” issues I found in my earlier testing I cannot reproduce the symptoms reported in this topic.

@sith Lord Goz – can you tell me the steps I must follow to cause the “PHP Fatal error” you reported? Thanks!

I have uploaded a new MLA Development Version dated 20160727 that fixes the View editor “Media” button I described in my earlier post. To get the Development Version, follow the instructions in this earlier topic:

Shortcode not working in (special) widget

It would be great if you can install the Development Version and let me know how it works for you. If there are other compatibility problems you can help me find I would be most grateful. Thanks for your help and for your patience.

@david Lingren
For me, it was having Toolset Types, Views and MLA all active, then going to a Page, editing in WYSWYG mode, then clicking the “Views” button to bring up a modal window to select/insert a View. That threw an error and looking at the log I saw it was the fatal error I mentioned.

@sith Lord Goz,

Thanks for your update with the additional explanation. I have just re-tested this as best I can and I do not see the Fatal Error using the latest MLA Development Version.

It would be great if you can install the Development Version and let me know how it works for you. If there are other compatibility problems you can help me find I would be most grateful. Thanks for your help.

I have released MLA version 2.32, which corrects the defects I was able to find in support for the Toolset family of plugins.

I am marking this topic resolved, but please update it if you find any other issues with the interaction between MLA and the Toolset family.