Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timezone not found in database #9

Open
thoni56 opened this issue Sep 21, 2015 · 5 comments
Open

Timezone not found in database #9

thoni56 opened this issue Sep 21, 2015 · 5 comments

Comments

@thoni56
Copy link

thoni56 commented Sep 21, 2015

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
Copy link
Owner

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

@thoni56
Copy link
Author

thoni56 commented Sep 21, 2015

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 lcdservices reopened this Sep 21, 2015
@lcdservices
Copy link
Owner

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
Copy link
Author

thoni56 commented Sep 21, 2015

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
Copy link
Author

thoni56 commented Sep 21, 2015

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants