Skip Navigation

[Resolved] the folder /Command -> /command

This support ticket is created 5 years, 9 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 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: 

This topic contains 10 replies, has 2 voices.

Last updated by Waqar 5 years, 6 months ago.

Assisted by: Waqar.

Author
Posts
#1206578

We run IIS and the case sensitivity of the change in 3.1.2 to 3.2 has caused a 500 error. The autoloader is looking for /Command/delete_obsolete_version_number_option.php when it will never see it because IIS is not case sensitive. You would need to change the folder back to /command/delete_obsolete_version_number_option.php (lowercase c in command) and the fix the reference in the classmap

#1206880

Hi,

Thank you for sharing this and I've passed on these findings to the concerned team for further review.

Appreciate you brought this forward and I'll keep you updated with the progress through this ticket.

regards,
Waqar

#1211408

Wondering if there has been any motion on this

#1211715

Hi,

Thanks for writing back.

Based on your report, there are some changes planned in future releases, which should address this case sensitivity issue. But, I'm afraid, I don't have a time estimate to share at the moment.

I'll update you through this ticket once this has been implemented, meanwhile, were you able to update the Types plugin manually?

regards,
Waqar

#1234430

We are moving hosts to pantheon and in some of our initial tests are seeing the same issues. If the old plugin is there an issue arises with deploying with GIT.

#1234780

Hi,

This is planned to be improved in the next major release of Types ( version 3.3 ) and I'll update you through this ticket, once it is out.

Until then, you'll need to manually adjust the folder name in such cases, I'm afraid.

regards,
Waqar

#1235206

wonderful news

#1240591

Is there a time frame for the update that will fix this issue? We are currently unable to update since 3.1.2, which is now preventing us from updating WP core. In our dev env we are seeing quite a bit of JS errors in 3.1.2 version of the plugin. Particularly conflicting with Yoast SEO plugin. Thanks!

#1240790

Hi there,

I'm afraid, I don't have a time estimate to share for the release of Types 3.3, but have you tried updating to the latest available version and use any of the following workarounds:

1. Deactivate and delete the existing 3.1.2 version of the plugin and then directly install the latest 3.2.7 version.
( https://toolset.com/download/toolset-types/#changelog )

OR

2. Manually copy the contents of the folder "/Command/delete_obsolete_version_number_option.php" into a new parallel folder of the same name but with a small "c" "/command/delete_obsolete_version_number_option.php"

regards,
Waqar

#1241212

so:
1. can not deactivate on over 10k installs, also don't have sftp access, everything is version controlled
2. hmmm..so i have to change my computer settings to allow 2 folders named the same...

last options is patching your plugin to do a huge search are replace.. still not really a good solution.

#1241317

Hi there,

I'd like to update that Types version 3.3 has been released.

You're welcome to update to this latest version and let me know how it goes.

regards,
Waqar