search

lcdservices / CiviEvent-Joomla-Module

Display a list of events in a Joomla module position, based on various filter criteria and display options.
6 stars 4 forks source link

Timezone not found in database #9

Open thoni56 opened 8 years ago

thoni56 commented 8 years ago

On a Joomla 3.4.4/CiviCRM 4.6.7 I get the error message in the attached screenshot when trying to configure a module. Any hints if this is a CiviEvent-Joomla-Module problem?

image

lcdservices commented 8 years ago

I don't think this is an issue with the module. We don't create a DateTime object anywhere in the module code.

thoni56 commented 8 years ago

Are you sure? here is some indication that a changed behaviour between 3.4.3 and 3.4.4 may be the cause of this. If not caused by the module in it self, perhaps some hints for the Joomla developers can be found...

I confirmed that the module displayed its properties fine in 3.4.3 by running of a backup that I restored. Then upgraded to 3.4.4 and the error occurred.

lcdservices commented 8 years ago

I think you're right -- it's related to that issue. I've pushed up a patch to address it. However -- I don't think you'll be able to edit your existing module; you'll have to add a new module, select this module type, and then reconfigure it.

The problem is that previously calendar fields (date selection fields) could have a string default value -- I had used the text "Select" as the default. The changes in J3.4.4 require that any value be a valid date value, so string text is not allowed. But any existing instances of this module you already created would have that default value stored in the DB, and so will error. That's unfortunate (and a bit annoying that Joomla made the change in a minor release), but there's no easy way to fix it.

Can you install the update, test, and confirm.

thoni56 commented 8 years ago

Yes, you could see some irritation in the discussions around that change...

I've installed it on the upgraded backup and it seems to work there. Thanks for looking into it and fixing it!

thoni56 commented 8 years ago

I also managed to recover my old module by fixing up the paramsvalue for it in the database.