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

Make language support mandatory #38

Closed
kikmedia opened this issue Jan 31, 2013 · 5 comments
Closed

Make language support mandatory #38

kikmedia opened this issue Jan 31, 2013 · 5 comments
Milestone

Comments

@kikmedia
Copy link
Contributor

On creating a new metamodel you can skip the translations settings. After that and on trying to create attributes, I'm getting a blank page, leaving something like

[[31-Jan-2013 13:50:14 UTC] PHP Fatal error:  Declaration of MetaModelAttributeGeoProtection::getFilterOptions() must be compatible with that of IMetaModelAttribute::getFilterOptions() in /is/htdocs/wp11097041_TUWBIMV6WA/www/htdocs/cms/2_11/system/modules/metamodelsattribute_geoprotection/MetaModelAttributeGeoProtection.php on line 29]

in my server log. So I wondered if we should make a default language mandatory,

@HenryVolkmer
Copy link
Contributor

Stichwörter: namespaces/autoloading und "use" -statement

@discordier
Copy link
Member

There were API changes to which the geoprotection attribute has not yet been adapted to.

@kikmedia
Copy link
Contributor Author

Ah, I see. Thanks @discordier (and I didn't figure out what namespaces/autoloading/use means in this context @HenryLamorski)

@discordier
Copy link
Member

Fixed in MetaModels/attribute_geoprotection@35004c4

And thanks for using MetaModels. :)

@discordier
Copy link
Member

On the original topic, the first language specified should be made "mandatory" automatically.

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

3 participants