Skip Navigation

[Resolved] Newer Toolset Update Crashed my Plugin

This support ticket is created 5 years, 2 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 6 replies, has 2 voices.

Last updated by benjaminJ-3 5 years, 2 months ago.

Assisted by: Shane.

Author
Posts
#1345187

I am trying to: Keep my plugin working while being able to update Toolset

Link to a page where the issue can be seen: hidden link

I'm not sure which Toolset Update is causing the issue but it was within the last 6 months. I'm using

get_post_meta($_REQUEST['cptID'],"wpcf-special-offer",true)

to pull in data for a form. When I update Toolset the form no longer works. Is there anything in the newest update that would affect how I'm updating this form info? I don't know for sure that the code above is the specific issue but I do know that when I update toolset my plugin stops working.

#1345197

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Benjamin,

Thank you for getting in touch.

The update shouldn't have affected this. However you can use
get_post_meta($_GET['cptID'],"wpcf-special-offer",true)

Using $_GET to get the values of the query string.

Thanks,
Shane

#1345207

Ya, I guess that is not the issue... I'm totally baffled as to what toolset could have changed to affect my plugin. My plugin is pretty simple overall. Is there a developer level change log I can see for toolset?

#1345209

Actually with further testing I've found out that it's the toolset views that is causing a conflict.

#1345215

Ok, I found the new console error that comes up when I update Views:

Uncaught ReferenceError: wpv_pagination_local is not defined
at c.validator.submitHandler (VM407 custom_script.js:108)
at e (VM411 jquery.validate.js:14)
at HTMLFormElement.<anonymous> (VM411 jquery.validate.js:14)
at HTMLFormElement.dispatch (VM378 jquery.js:3)
at HTMLFormElement.r.handle (VM378 jquery.js:3)

#1346309

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Benjamin,

No we actually don't have a developer level log.

Could you send me the code that you are using so that I can get a full context of what the code is suppose to do.

Perhaps we can work on a fix?

Also the error you sent is a JS error, it should have anything to do with the php function form your initial message. However for this JS error I would disable the non-toolset plugins to see if there is a conflict with any other installed plugin.

Thanks,
Shane

#1346355

My issue is resolved now.

I was calling Toolset's reference to wpv_pagination_local.front_ajaxurl so that I would not have to call Ajax twice. You must have updated your code structure and changed how you are calling Ajax.