Skip Navigation

[Resolved] Cred spinner and message

This support ticket is created 3 years, 8 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.

Our next available supporter will start replying to tickets in about 2.05 hours from now. Thank you for your understanding.

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 23 replies, has 2 voices.

Last updated by Shane 3 years, 6 months ago.

Assisted by: Shane.

Author
Posts
#2027521
Errore toolset.PNG

Hi David,
if you not logged into wordpress (only into area riservata) the spinner not load.
I show error into JQuery (i attach screenshot).
Thanks

#2027557

Shane
Supporter

Languages: English (English )

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

Hi David,

I'm able to see the errors while not logged in as admin.

This could be why the spinner isn't loading. I would like to rule out the possibility of this being a plugin conflict.

Can you temporarily disable all the non-toolset plugins and check again. Secondly we have update out Toolset plugins so can you go to Plugins -> Add New and click on Commercial, then on this page click the "Check for Updates" button then perform an update on the Toolset plugins to see if this resolves the issue as well.

Thanks,
Shane

#2028219
Errore toolset.PNG

Hi Shane,
i tried to update the plugin but not i show this error when i click save (before updating the error was not shown).
Regards

#2028707

Shane
Supporter

Languages: English (English )

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

Hi David,

Let us tackle this an issue at a time.

Right now we need to verify that the spinner works for the demo user as it works for admins when logged in.

Have you disabled all the non-toolset plugins to check and verify that the spinner works for those demo users? If it still doesn't work I will need to take a copy of the site to test further where I can safely strip the site down to see what is happening here and causing the javascript error on the site.

Please perform the plugin test for me and let me know as soon as possible.

Thanks,
Shane

#2035507

Hi Shane,
i tried to disable all plugin (Toolset and PrivateContent only active) but the problem not fix.
Regards

#2037195

Shane
Supporter

Languages: English (English )

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

Hi David,

I've grabbed a copy of your site for further testing here locally.

Will provide an update shortly.

Thanks,
Shane

#2037315

Shane
Supporter

Languages: English (English )

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

Hi David,

I have some Good News. Since the update the spinner is now working for users who are not admin.

I've tested it and it works correctly. The issue I see now is for the fields that are empty that are preventing the form from being submitted.

I'm checking now to see if I can replicate the issue you are having with the Form fields on a fresh install.

Thanks,
Shane

#2041597

Shane
Supporter

Languages: English (English )

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

Hi David,

I'm able to replicate the issue where you are getting message “You can only upload an image file” when submitting your edit form.

I've escalated the issue to our second tier supporters for further checks on this one.

I'll provide an update as soon as I get any from them.

Thanks,
Shane

#2043117

Shane
Supporter

Languages: English (English )

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

Hi David,

This is actually a known issue and an erratas page was created for it below.
https://toolset.com/errata/validation-error-if-image-field-is-blank-when-not-using-wp-media-uploader/

You can keep up to date with this issue by monitoring this page. At this point there is nothing else I can do since out development team is aware of the issue.

Thanks,
Shane