Re: [Radiant] Content Internationalization
Hi Ben I discussed this issue with a friend of mine involved in many localizations (translation company)... he said exactly what you wrote. Few , actually very few sites needs a true mixin of multi-languages contents: one in which the visitor enter in english and need to get a spanish version of one article... generally, the visitor wants to choose one language and stick to it... It would be better to work on a good initial design in the default language, then buying or building admin tools that help in duplicating the default site, localizing all existing contents to another language, and deploying multi sub-domains , one for each language.. Radiant is lite and simple to use, trying to add in core multi- language capabilities will transform it into a 'refinery' ... better keep it clean, small and green adding extensions... (I have been deeply looking into the Zope/Plone CMS for a customer... an example of refinery) That's what I am going to do for my next customer : default site :en http://www.mycustomersite.com - proxy URL to http://www.mycustomersite.com/en/ duplicate to sub-domain http://fr.mycustomersite.com - proxy URL to http://www.mycustomersite.com/fr/ ,localizing the content .. and so on why not a localization extension wich will had a language bar view and manage all localization parameters erwin On 9 Mar 2009, at 22:59, Ben Still wrote: Hi Doug, We've done a number of sites now that need to cover two or three markets. I thought it might be useful to share this as it's something we've come up against a few times. I realise that you're asking about internationalisation as in having an identical page that can render in different languages. In sites we've worked on, this often also means different prices and product fact sheets etc. The easiest thing from a development perspective is having one site, then make it smart to render out the different flavour depending on URL or cookie. We've run into two issues on that. First is the customer wanting slightly different behaviour or structure on one but not the others. A few changes are manageable, but as you can imagine this can get out of control and become a bit of a nightmare of localisation hacks. The second issue is SEO and localisation. Apparently physical location is a big deal. If you want to rank well with Japanese customers, use a Japanese TLD and host out of a Japanese rather than say a US datacentre. I realise in your example the Spanish version might well be for Spanish rather than English speakers in the US- this example is for different geographic markets. So, faced with those two issues, we typically make several different sites with one code repository. We've found this much easier in the long run. Capistrano manages the updates to each site so code remains the same, but the content is separate. A bit of a drag in that the content editor has to go to different /admins, but allows for flexible changes to structure and content, as well as addressing the SEO issue. Anyway- hope that helps someone at some stage regards Ben Doug Bryant wrote: I'm currently looking at integrating radiant cms into our site. One of the requirements we have coming down the pipeline soon is internationalization. Is there a best practice anyone could suggest for internationalization of the content with Radiant? I ran across a couple of posts from May 2007 about doing this, but am checking because I don't know if this is still the suggested route. Does the rails 2.3 feature of rendering internationalization snippets change any recommendations? (:render :partial = foo would render _foo.en.html or _foo.es.html depending on current locale) http://www.mail-archive.com/radi...@lists.radiantcms.org/ msg04509.html http://www.mail-archive.com/radi...@lists.radiantcms.org/ msg04535.html What I envision is splitting out the content part of our app and integrating it into Radiant. We have someone who would then be able to translate maintain the spanish version of the website. Content does not presently change too frequently, but would it if didn't require a complete application redeploy just to update a some portion of the content. Any suggestions? All feedback is greatly appreciated. Doug === Doug Bryant doug.bry...@milemeter.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Ben Still | Red Ant | office +612 9267 8300 ext 208 | mobile 0425 294 271 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post:
Re: [Radiant] Content Internationalization
Yves Dufour wrote: Hi Ben I discussed this issue with a friend of mine involved in many localizations (translation company)... he said exactly what you wrote. Few , actually very few sites needs a true mixin of multi-languages contents: one in which the visitor enter in english and need to get a spanish version of one article... generally, the visitor wants to choose one language and stick to it... It would be better to work on a good initial design in the default language, then buying or building admin tools that help in duplicating the default site, localizing all existing contents to another language, and deploying multi sub-domains , one for each language.. Radiant is lite and simple to use, trying to add in core multi-language capabilities will transform it into a 'refinery' ... better keep it clean, small and green adding extensions... (I have been deeply looking into the Zope/Plone CMS for a customer... an example of refinery) That's what I am going to do for my next customer : default site :en http://www.mycustomersite.com - proxy URL to http://www.mycustomersite.com/en/ duplicate to sub-domain http://fr.mycustomersite.com - proxy URL to http://www.mycustomersite.com/fr/ ,localizing the content .. and so on why not a localization extension wich will had a language bar view and manage all localization parameters I just have a localization bar that only finds if the article exists in another language (based on the convention that all languages have the same slug with only a different language portion /en/article or /fr/article and so on. It is assumed that /en /fr /jp will have completely different content in my case. Essentially, it is also assumed that the language maintainers are different people. Further, not all content is available in all supported languages. The loss is that the slug will always be in a single language. I use this as demonstrated on: http://t-engine.onghu.com/en/articles/booting-t-engine-from-usb/ (thebar shows 'en' and 'th') On another page: http://t-engine.onghu.com/cn/articles/te-recommended-reading/ it shows 'cn' and 'en' and so on. Cheers, Mohit. 3/10/2009 | 4:08 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] site_watcher error
Hello again, I installed the site_watcher extension and ran the migration. When going to the dashboard I get this error: ActiveRecord::StatementInvalid in Admin/dashboard#index Showing vendor/extensions/site_watcher/app/views/admin/dashboard/ _popular_pages.html.haml where line #1 raised: Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 2' at line 1: SELECT * FROM `page_requests` WHERE (count_created 1 and (ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 25 Extracted source (around line #1): 1: - @popular_pages = PageRequest.find_popular 2: - unless @popular_pages.blank? 3: #popular_pages.dashboard_module 4: %h2 Popular Pages Trace of template inclusion: /vendor/extensions/dashboard/app/views/ admin/dashboard/index.html.haml ... I haven't touched haml before, so a bit unsure how to proceed. TIA, Elle ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Content Internationalization
HI Mohit Very interesting ... how did you proceed when entering the articles and setting the different language portions ... no core modification ? (DB records) could this be managed in an extension ? Yves (erwin in brittany dialect..) On 10 Mar 2009, at 09:08, Mohit Sindhwani wrote: Yves Dufour wrote: Hi Ben I discussed this issue with a friend of mine involved in many localizations (translation company)... he said exactly what you wrote. Few , actually very few sites needs a true mixin of multi-languages contents: one in which the visitor enter in english and need to get a spanish version of one article... generally, the visitor wants to choose one language and stick to it... It would be better to work on a good initial design in the default language, then buying or building admin tools that help in duplicating the default site, localizing all existing contents to another language, and deploying multi sub-domains , one for each language.. Radiant is lite and simple to use, trying to add in core multi- language capabilities will transform it into a 'refinery' ... better keep it clean, small and green adding extensions... (I have been deeply looking into the Zope/Plone CMS for a customer... an example of refinery) That's what I am going to do for my next customer : default site :en http://www.mycustomersite.com - proxy URL to http://www.mycustomersite.com/en/ duplicate to sub-domain http://fr.mycustomersite.com - proxy URL to http://www.mycustomersite.com/fr/ ,localizing the content .. and so on why not a localization extension wich will had a language bar view and manage all localization parameters I just have a localization bar that only finds if the article exists in another language (based on the convention that all languages have the same slug with only a different language portion /en/article or / fr/article and so on. It is assumed that /en /fr /jp will have completely different content in my case. Essentially, it is also assumed that the language maintainers are different people. Further, not all content is available in all supported languages. The loss is that the slug will always be in a single language. I use this as demonstrated on: http://t-engine.onghu.com/en/articles/booting-t-engine-from-usb/ (thebar shows 'en' and 'th') On another page: http://t-engine.onghu.com/cn/articles/te-recommended-reading/ it shows 'cn' and 'en' and so on. Cheers, Mohit. 3/10/2009 | 4:08 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] site_watcher error
On Mar 10, 2009, at 5:47 AM, Elle Meredith wrote: Hello again, I installed the site_watcher extension and ran the migration. When going to the dashboard I get this error: ActiveRecord::StatementInvalid in Admin/dashboard#index Showing vendor/extensions/site_watcher/app/views/admin/dashboard/ _popular_pages.html.haml where line #1 raised: Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 2' at line 1: SELECT * FROM `page_requests` WHERE (count_created 1 and (ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 25 Extracted source (around line #1): 1: - @popular_pages = PageRequest.find_popular 2: - unless @popular_pages.blank? 3: #popular_pages.dashboard_module 4: %h2 Popular Pages Trace of template inclusion: /vendor/extensions/dashboard/app/views/ admin/dashboard/index.html.haml ... I haven't touched haml before, so a bit unsure how to proceed. The error is coming from the SQL generated in the PageRequest.find_popular method. I don't generally use MySQL, so I never saw this until now, but I've fixed it and it should work for you if you pull the latest from github. -Jim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] site_watcher error
Hi Jim did you tried to run the SQL command in a console (in phpmyadmin) to see what's wrong and what should be the correct command ... erwin On 10 Mar 2009, at 14:28, Jim Gay wrote: On Mar 10, 2009, at 5:47 AM, Elle Meredith wrote: Hello again, I installed the site_watcher extension and ran the migration. When going to the dashboard I get this error: ActiveRecord::StatementInvalid in Admin/dashboard#index Showing vendor/extensions/site_watcher/app/views/admin/dashboard/ _popular_pages.html.haml where line #1 raised: Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 2' at line 1: SELECT * FROM `page_requests` WHERE (count_created 1 and (ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 25 Extracted source (around line #1): 1: - @popular_pages = PageRequest.find_popular 2: - unless @popular_pages.blank? 3: #popular_pages.dashboard_module 4: %h2 Popular Pages Trace of template inclusion: /vendor/extensions/dashboard/app/views/ admin/dashboard/index.html.haml ... I haven't touched haml before, so a bit unsure how to proceed. The error is coming from the SQL generated in the PageRequest.find_popular method. I don't generally use MySQL, so I never saw this until now, but I've fixed it and it should work for you if you pull the latest from github. -Jim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] site_watcher error
On Mar 10, 2009, at 9:48 AM, Yves Dufour wrote: Hi Jim did you tried to run the SQL command in a console (in phpmyadmin) to see what's wrong and what should be the correct command ... The error is in the message below with the full SQL query. I tried running it in a mysql GUI and just added back ticks around the `ignore` fields and it worked. Here's the the change http://github.com/saturnflyer/radiant-site_watcher-extension/commit/757f273b6051d286ea04d92443c1d31e74d4a726 erwin On 10 Mar 2009, at 14:28, Jim Gay wrote: On Mar 10, 2009, at 5:47 AM, Elle Meredith wrote: Hello again, I installed the site_watcher extension and ran the migration. When going to the dashboard I get this error: ActiveRecord::StatementInvalid in Admin/dashboard#index Showing vendor/extensions/site_watcher/app/views/admin/dashboard/ _popular_pages.html.haml where line #1 raised: Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 2' at line 1: SELECT * FROM `page_requests` WHERE (count_created 1 and (ignore is NULL or ignore = 0)) ORDER BY count_created DESC, virtual ASC LIMIT 25 Extracted source (around line #1): 1: - @popular_pages = PageRequest.find_popular 2: - unless @popular_pages.blank? 3: #popular_pages.dashboard_module 4: %h2 Popular Pages Trace of template inclusion: /vendor/extensions/dashboard/app/ views/admin/dashboard/index.html.haml ... I haven't touched haml before, so a bit unsure how to proceed. The error is coming from the SQL generated in the PageRequest.find_popular method. I don't generally use MySQL, so I never saw this until now, but I've fixed it and it should work for you if you pull the latest from github. -Jim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Radiant Digest, Vol 36, Issue 10
Thanks Sean,
I though Radiant uses mechanize because I started out with a empty
gems folder. When I did gem install radiant rspec and rspec-rails
were installed along with radiant. At this point I have only 3 gems.
And if I now do gem update then many gems start to get downloaded,
only to get stuck with mechanize. So I guess either rspec or rspec-
rails is the culprit?
Ken
Message: 4
Date: Sat, 07 Mar 2009 12:44:30 -0500
From: Sean Cribbs seancri...@gmail.com
Subject: Re: [Radiant] Does Radiant use mechanize gem?
To: radiant@radiantcms.org
Message-ID: 49b2b27e.8010...@gmail.com
Content-Type: text/plain; charset=UTF-8; format=flowed
Ken,
No, Radiant does not require mechanize, but you might have something
installed that requires it?
Sean
K H wrote:
Hi.
I have Radiant site on Dream Host and have local gem installation.
When I do gem update it seems the mechanize gem is downloaded
because Radiant requires it? The problem is the mechanize gem never
successfully installs. I get the error message pasted below, and when
I contacted DH support, they said they can't make libxslt available,
that I would have to compile the mechanize gem for linux machine and
upload it myself. But I do not have access to linux machine. Is there
a way to get around / prevent the mechanize gem from getting stuck?
Thanks.
Ken
-error message-
[wolverine]$ gem update
Updating installed gems
Updating mechanize
Building native extensions. This could take a while...
ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError)
ERROR: Failed to build gem native extension.
/usr/bin/ruby1.8 extconf.rb update
checking for libxml/parser.h in
/opt/local/include/,/opt/local/include/libxml2,/usr/include/
libxml2,/usr/include,/usr/local/include/libxml2,/usr/include/
libxml2...
yes
checking for libxslt/xslt.h in
/opt/local/include/,/opt/local/include/libxml2,/usr/include/
libxml2,/usr/include,/usr/local/include/libxml2,/usr/include/
libxml2...
no
libxslt is missing. try 'port install libxslt' or 'yum install
libxslt'
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/ruby1.8
--with-xml2-dir
--without-xml2-dir
--with-xml2-include
--without-xml2-include=${xml2-dir}/include
--with-xml2-lib
--without-xml2-lib=${xml2-dir}/lib
--with-xslt-dir
--without-xslt-dir
--with-xslt-include
--without-xslt-include=${xslt-dir}/include
--with-xslt-lib
--without-xslt-lib=${xslt-dir}/lib
Gem files will remain installed in
/home/kenhan/.gems/gems/nokogiri-1.2.1 for inspection.
Results logged to
/home/kenhan/.gems/gems/nokogiri-1.2.1/ext/nokogiri/gem_make.out
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Radiant Digest, Vol 36, Issue 10
Again, AFAIK this is not radiant's dependencies. Can you provide a list
of all the gems you have installed?
$ gem list
Sean
K H wrote:
Thanks Sean,
I though Radiant uses mechanize because I started out with a empty
gems folder. When I did gem install radiant rspec and rspec-rails
were installed along with radiant. At this point I have only 3 gems.
And if I now do gem update then many gems start to get downloaded,
only to get stuck with mechanize. So I guess either rspec or
rspec-rails is the culprit?
Ken
Message: 4
Date: Sat, 07 Mar 2009 12:44:30 -0500
From: Sean Cribbs seancri...@gmail.com
Subject: Re: [Radiant] Does Radiant use mechanize gem?
To: radiant@radiantcms.org
Message-ID: 49b2b27e.8010...@gmail.com
Content-Type: text/plain; charset=UTF-8; format=flowed
Ken,
No, Radiant does not require mechanize, but you might have something
installed that requires it?
Sean
K H wrote:
Hi.
I have Radiant site on Dream Host and have local gem installation.
When I do gem update it seems the mechanize gem is downloaded
because Radiant requires it? The problem is the mechanize gem never
successfully installs. I get the error message pasted below, and when
I contacted DH support, they said they can't make libxslt available,
that I would have to compile the mechanize gem for linux machine and
upload it myself. But I do not have access to linux machine. Is there
a way to get around / prevent the mechanize gem from getting stuck?
Thanks.
Ken
-error message-
[wolverine]$ gem update
Updating installed gems
Updating mechanize
Building native extensions. This could take a while...
ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError)
ERROR: Failed to build gem native extension.
/usr/bin/ruby1.8 extconf.rb update
checking for libxml/parser.h in
/opt/local/include/,/opt/local/include/libxml2,/usr/include/libxml2,/usr/include,/usr/local/include/libxml2,/usr/include/libxml2...
yes
checking for libxslt/xslt.h in
/opt/local/include/,/opt/local/include/libxml2,/usr/include/libxml2,/usr/include,/usr/local/include/libxml2,/usr/include/libxml2...
no
libxslt is missing. try 'port install libxslt' or 'yum install
libxslt'
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/ruby1.8
--with-xml2-dir
--without-xml2-dir
--with-xml2-include
--without-xml2-include=${xml2-dir}/include
--with-xml2-lib
--without-xml2-lib=${xml2-dir}/lib
--with-xslt-dir
--without-xslt-dir
--with-xslt-include
--without-xslt-include=${xslt-dir}/include
--with-xslt-lib
--without-xslt-lib=${xslt-dir}/lib
Gem files will remain installed in
/home/kenhan/.gems/gems/nokogiri-1.2.1 for inspection.
Results logged to
/home/kenhan/.gems/gems/nokogiri-1.2.1/ext/nokogiri/gem_make.out
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Caching twitter updates
Victor, If you can pull the Twitter updates in via RSS or Atom, you can use the feed_reader extension, which caches the feed data and utilizes ETags and Last-Modified headers to reduce bandwidth consumption. http://github.com/seancribbs/radiant-feed-reader-extension Sean Victor Zuniga wrote: Hello, I am hoping someone can point me in the right direction on this. We are using the twitter widget (Javascript) to display updates on our front page. Lately, we have experienced situations where the widget would not display the updates at all. We contacted twitter support and they basically said we need to cache the API responses in our website. I thought that was being cached through the Page Cache built-in on Radiant but maybe I am misunderstanding the two functionalities. Has anyone else experienced this behavior? Any information/feedback you can provide will be appreciated. Thanks, Victor ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Caching twitter updates
Hello, I am hoping someone can point me in the right direction on this. We are using the twitter widget (Javascript) to display updates on our front page. Lately, we have experienced situations where the widget would not display the updates at all. We contacted twitter support and they basically said we need to cache the API responses in our website. I thought that was being cached through the Page Cache built-in on Radiant but maybe I am misunderstanding the two functionalities. Has anyone else experienced this behavior? Any information/feedback you can provide will be appreciated. Thanks, Victor ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Caching twitter updates
On Tue, Mar 10, 2009 at 1:58 PM, Victor Zuniga vzun...@westervillelibrary.org wrote: Hello, I am hoping someone can point me in the right direction on this. We are using the twitter widget (Javascript) to display updates on our front page. Lately, we have experienced situations where the widget would not display the updates at all. We contacted twitter support and they basically said we need to cache the API responses in our website. I thought that was being cached through the Page Cache built-in on Radiant but maybe I am misunderstanding the two functionalities. Radiant generates the HTML and Javascript. The client's web browser executes that javascript, which talks to Twitter and displays the updates. Note that the client's web browser communicates with twitter in this case. Not Radiant. The twitter data never touches Radiant -- so it has no way to cache it. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] share_layouts extension and filters
Hello everyone, I have a question about the share_layouts extension. I am using it on a site that has the defaults.page.filter set to Textile. Consequently the content generated by my custom controllers and views is rendered out as Textile, which is not what I had in mind. Is there a way to override this behaviour? Can I set the page part filter from my extension somehow? I have read Sean's post about creating 'endpoint' pages, but my routes are dynamic so I can't create pages/page_parts for them. Cheers, Remko ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] share_layouts extension and filters
That seems like a common enough use-case that the expected behavior would be to have no filter. I'd gladly take a patch to fix that. Sean Remko Steenstra wrote: Hello everyone, I have a question about the share_layouts extension. I am using it on a site that has the defaults.page.filter set to Textile. Consequently the content generated by my custom controllers and views is rendered out as Textile, which is not what I had in mind. Is there a way to override this behaviour? Can I set the page part filter from my extension somehow? I have read Sean's post about creating 'endpoint' pages, but my routes are dynamic so I can't create pages/page_parts for them. Cheers, Remko ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
