aissac / radiant-globalize2-extension Goto Github PK

Thanks for this great extension! We have been using it extensively.

However, we have just run into this issue which seems to be a biggie if you have to update the published date for blog posts routinely, and want to use Radiant's built-in mechanism for doing so:

Setting the Radiant configuration page.edit.published_date? to true (as described here: http://wiki.github.com/radiant/radiant/change-a-pages-publication-date), causes pages to become uneditable.

I can't display any translated article/page. I see strange sql queries like this:

   SELECT `pages`.* FROM `pages` INNER JOIN page_translations on page_translations.page_id = pages.id WHERE ((virtual = 0) and (status_id = 100)) AND ((page_translations.locale = '--- :en\n') AND (`pages`.parent_id = 4)) ORDER BY published_at DESC, pages.virtual DESC LIMIT 1

After some investigation I managed to work around this issue by editing file lib/globalize2/page_extensions.rb and adding .to_s in two places where find queries are created

I've also have problems with conversion symbol to string, but it's already posted as an issue

Really great work :-) What would be needed to make this compatible to the chronicle (or any oder versioning) extension?

page:each does not work with attributes

http://gist.github.com/560880

ive narrowed this down to the globalize2 version that is bundled (< v0.1.1). the errors go away with the globalize1 v0.1.1 on github.

But this breaks the globalize2 radiant extension in other ways:

undefined method update_globalize_record' for classPage'

i am seeing this on a fresh install of rc2

globalize2/lib/globalize2/page_extensions.rb:64:in `url'

and basically anywhere else I18n.locale is used to interpolate a string

1 comment Created 6 minutes ago by jerrod | edit
i am seeing this on a fresh install of rc2 using the 0.9 branch of globalize2

globalize2/lib/globalize2/page_extensions.rb:64:in `url'

and basically anywhere else I18n.locale is used to interpolate a string