All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Arabic url title
| Status | Resolved |
| Add-on / Version | Publisher 1611 |
| Severity | |
| EE Version | 2.11 |
Mohammed Al-Faisal
Apr 25, 2016
Description:
I have just installed publisher on a fresh EE install and set my default language to arabic and added english as a second language, when I tried to publish a new entry I got an error “Unable to create valid URL Title for your entry” when using arabic for the URL Title field. EE by default doesn’t support arabic in URL Titles and what I understood from Publisher’s web site is that it facilitates translating URLs.
Please advice to the current way to allow arabic URLs for entries.
Detailed steps to reproduce the issue:
1. Fresh EE install.
2. Installed Publisher.
3. Set arabic as default language in Publisher.
4. Created new channel and channel fields.
5. Tried adding new entry with arabic URL Title.
6. Got “Unable to create valid URL Title for your entry” error.
BoldMinded (Brian)
Publisher will translate URLs, but its still within the bounds of EE’s rules. Translated URLs effectively means the URL Title is just different for each language, it doesn’t add any additional translation capabilities or support for characters that EE does not support. Sorry for the confusion.
BoldMinded (Brian)
Just making sure you got this message. Going to close the ticket as this isn’t a bug nor something I can fix.