Hi,

Just checking now. I've put the debug language. Note that I am using en-GB by default in back end and front end.

All the four book-it language files .ini have parsing errors, according to the Debug language. A lot of key strings have space " " or period "." instead of underscore "_", this is what is causing so many parsing errors.

I stripped most of the .ini files to remove the parsing errors, and kept the dates strings. Now I have none of the parsing issues.
Then the date appears more properly:


But still, same error, I cannot create a bookable item... IT seems like it is not a translation issue.

It prevents me to complete my test, so I can not recommend it to my customers. Are you able to reproduce the problem, or do you request more details?

Kind regards,
Hervé

Hello,

can you send admin and ftp acces to your website to Diese E-Mail-Adresse ist gegen Spambots geschützt! Du musst JavaScript aktivieren, damit Du sie sehen kannst. , so we can check it?
Please, add there link to this topic.

Hi maju,

I wish I could, but I am testing on XAMPP (local server) and the extranet is on a private network... Am I getting stuck here?

Ok, if you repaired language file, what error do you get for now? Can you check logs?
That old error:
500 - An error has occurred.
DateTime::__construct() [datetime.--construct]: Failed to parse time string (ThuAMUTCE_May+0000RMayAMUTC_0+0000411) at position 0 (T): The timezone could not be found in the database

should be already solved if there are corrected date formats.

And you can not create bookable item or can not book it? If you have free version, you are limited only to two bookable items. You should be not able to create more. Are you sure, there are no bookable items at the moment?

Thank you for your reply.
Yes, I am sure, no existing bookable item.

But I just put back "Debug language" to No, and tried again. It is now working!!

And I have just tested installation and bookable item creation on another dev website, and it worked ok... without changing the language files!!

So I don't know what was wrong, and it is very annoying: if the error come back later, we still don't know why!! Php version? deprecated code?

Then I am getting back to complete my tests.

Kind regards,
Hervé

PHP version should be ok. We use similar version. For example I use 5.3.5 for tests.
The best will be to upload website to the internet if you will have same error again. Then we will be able (with ftp access) to find the problem in source code.

I don't remember anyone with similar problem.