Skip Navigation

[Resolved] Toolset trying to load script in /plugins/types/library/toolset/ > 404

This support ticket is created 7 years, 1 month 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by martijnH 7 years, 1 month ago.

Assisted by: Christian Cox.

Author
Posts
#577897
Duikcursussen voor beginners - Duikcentrum Tuimelaar Zwolle - Google Chrome.jpg

A taxonomy page hidden link is not showing correctly because of errors. See screenshot. It is trying to load js and css with an incorrect/not existing WP Types path (/plugins/types/library/).

The strange thing is that this only occurs when I am not logged in and not on other urls of the same taxony. For example hidden link.

I already disabled caching plugins (WP Rocket) and cleared browser cache, but that does nog solve the problem. Also checked if other websites I made with Types did have that path (/plugins/types/library/) but they did not.

Why does Types load js and css from a not existing path?

Thanks for your help!

#577901

By the way... when I am logged in, I see that the scripts are loaded from another path:
/plugins/types/vendor

Instead of:
/plugins/types/library/

#577904

Hi, let's try the following troubleshooting steps to narrow down the source of the problem:
- Deactivate, then completely delete the Types and Views plugins. Reinstall them from zip files you can download in your account area here on wp-types.com.
- If the problem was not resolved, temporarily activate a default theme like Twenty Seventeen and deactivate all plugins except Types and Views. If you need to use a plugin like Maintenance Mode for this test that's okay. Test the page again.
- If the problem was resolved, reactivate your theme and plugins one by one until the conflict is revealed.
- If the problem was not resolved, I'll need to do some additional investigation.

#578086

Problem resolved. An old htaccess file was uploaded by some else with some old code.
Thanks!