The solution I have implemented is as follows:
1. still have a configuration page, it is just not located as the first
page of the project structure. I usually have it like this
Start Page
anc_dyn_link
Home Page
anc_dyn_link
Technical Administration Page
anc_dyn_link
CSS
anc_dyn_link
JS
anc_dyn_link
Project Configuration Page
Instead of using rendertag or navigation area to get an element value from
the project configuration page, I just create an element on the page, and
reference the element to the element on the project configuration page.
This way, should the user desire to have different value for the element on
the page, they can severe the reference, and enter independent value.
I also wrote a plugin can retro active ELEMENT reference to do this
retroactively on projects that were using rendertag/navigation area, to
help them switch to the element reference method.
-Jian
On Friday, August 16, 2013 4:27:04 PM UTC-4, Joel Kinzel wrote:
>
> Yeah we don't have the TOC in navigation. We just use navigation areas to
> pull the settings from it. In order to have multiple sites in the same
> project, we need a way to have multiple settings pages as well. We found
> nav areas to be the "best" solution If you have another idea, I'm all ears.
>
> On Thursday, August 15, 2013 10:00:40 AM UTC-5, Jian Huang wrote:
>>
>> Hi Joel,
>>
>> The config page is something from the Best Practice Project. Well, the
>> practice of having the config page actually produces some issues.
>>
>> 1. The root node of the site navigation should really start at the Home
>> Page, not the TOC page because then extra navigation template and
>> processing are needed just to SKIP level 1. You can still have a config
>> page by access it via Pages.GetPage().
>>
>> I don't know enough about your project, but it is possible to use
>> con_translateCode to reference a page that contains txt_translateCode? No
>> navigation or rendertag is used. Simple project and easy maintenance.
>>
>> On Thursday, August 15, 2013 9:41:10 AM UTC-4, Joel Kinzel wrote:
>>>
>>> We have a very distributed environment, so keep that in mind when you
>>> read my solution.
>>>
>>>
>>> We have a "Table of Contents" page for each site in the CMS. On that
>>> page we allow users to enter site-wide information and settings (column
>>> alignment, breadcrumbs, taglines, search settings, translate, and others).
>>> In order to use Google Translate you need to generate unique code for each
>>> site. We have instructions for our users on how to do that.
>>>
>>> On the table of contents page, we then have a text area with "Deactivate
>>> text filter", ASCII Text", and "Do not convert characters to HTML"
>>> checked. This essentially gives the user an extremely stripped down editor.
>>> We ask them to paste the code snippet into that text area. We have another
>>> one for the meta tag that is required.
>>>
>>> We then have a navigation template that looks something like this:
>>> <%!!
>>> Context:CurrentPage.MainLink.OwnerPage.GetElementByName(txt_translateCode).Value
>>>
>>> !!%>
>>>
>>> The area is set to Level 1-1, Selected Only (this allows multi-site
>>> projects with unique settings)
>>>
>>> Then on each page, we just render that navigation area.
>>>
>>> Is it ideal? No, but it works for us!
>>>
>>>
>>> On Wednesday, October 27, 2010 11:45:24 AM UTC-5, psreddy wrote:
>>>>
>>>> Does any one implemented google translate in Reddot for the website?.
>>>> Please let me know your suggestions
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/reddot-cms-users.
For more options, visit https://groups.google.com/groups/opt_out.
