Hi All,
Would like to share that, now we are able to achieve our solution using
below RQL
const string MARK_DIRTY =
@"<ELEMENTS action=""Save""><ELT guid=""{0}"" /></ELEMENTS>";
project.ExecuteRQL(MARK_DIRTY.RQLFormat(elementGuid), RqlType.
SessionKeyInIodata);
So the flow was like.
1. Setting the text placeholder value using below code:
project.SetTextContent(elementGuid, project.LanguageVariants.Current,
"TextHtml", text);
2. Saving the placeholder value using RQL:
const string MARK_DIRTY =
@"<ELEMENTS action=""Save""><ELT guid=""{0}"" /></ELEMENTS>";
project.ExecuteRQL(MARK_DIRTY.RQLFormat(elementGuid), RqlType.
SessionKeyInIodata);
3. Releasing the page as mentioned below code:
newpage.Release();
And this solution helped us to change the content of text placeholder, save
the content and publish it automatically.
Which helped us to reduce half of the time we used to spent on the same
activity.
Thanks for everyones help.
Regards
Samridhi Dubey
On Wednesday, January 7, 2015 at 2:58:43 PM UTC+5:30, Hilmar Bunjes wrote:
> Hi Jian,
> yes, the IODATA including the attributes is added automatically by the
> SmartAPI. However, reading it again I'd expect to use "SessionKeyInIodata"
> (to put the session key into the IODATA block) as RqlType instead of
> "SessionKeyInProject".
>
> Best,
> Hilmar
>
> Am 06.01.2015 um 17:40 schrieb Jian Huang:
>
> Hilmar, not a problem. The library is an excellent addition to the
> community.
>
> Is Sami sending the RQL correctly? I noticed she did not include <IODATA
> loginguid="###" sessionkey="###">...</IODATA> in the RQL string.
>
> -Jian
>
> On Tuesday, January 6, 2015 10:15:40 AM UTC-5, Hilmar Bunjes wrote:
>>
>> Hi Sami,
>> I've just seen this discussion (and thanks to Jian for the very positive
>> statement about the SmartAPI :-) ). I'm wondering if the Page Preview looks
>> correctly if you clear the page cache before viewing the page.
>>
>> In the SmartAPI support Google group there was another question
>> from Abhishek Singhal with the same kind of problem. I'm not sure if you
>> are connected. The project.GetTextContent(...) is not the way you should
>> change an element. Unfortunately, it has been provided in the 1.0 version
>> and, therefore, we cannot remove it and stay API-compatible the same way.
>>
>> To change the element you should navigate to the page (get it either by
>> ID or GUID from the project) and then change the element of that page.
>>
>>
>> Best,
>> Hilmar
>>
>> Am Dienstag, 30. Dezember 2014 11:51:59 UTC+1 schrieb Sami Dubey:
>>>
>>> Hi Jian,
>>>
>>> Thank you for the information.
>>> Code we tried:
>>> const string MARK_DIRTY =
>>>
>>> @"<PAGEBUILDER><PAGES
>>> action=""pagevaluesetdirty""><PAGE sessionkey=""{0}""
>>> guid=""{1}""/></PAGES></PAGEBUILDER>";
>>> project.ExecuteRQL(
>>> MARK_DIRTY.RQLFormat(project.Session.SessionKey, pageGuid),RqlType
>>> .SessionKeyInProject);
>>> Still hardluck we are not able to see the changed content either via
>>> page preview or via publishing using .Net RQL.
>>> This is the only place where we are lacking, we are able to change the
>>> content of text placeholder dynamically. However we are not able to preview
>>> and publish. If any one has any idea please let us know.
>>>
>>> Thanks,
>>> Regards
>>> Samridhi Dubey
>>>
>>> On Wednesday, December 24, 2014 2:56:54 AM UTC+5:30, Jian Huang wrote:
>>>
>>>> Hi Samridhi,
>>>>
>>>> Since you are unable to provide template code that is responsible for
>>>> displaying the text element content. I assume you have no access or the
>>>> previously provided .NET RQL code runs outside of the system.
>>>>
>>>> Just run this RQL or whatever similar function this library provides to
>>>> clear page cache
>>>>
>>>> <PAGEBUILDER><PAGES action="pagevaluesetdirty"><PAGE
>>>> guid="###PAGEGUID###"/></PAGES></PAGEBUILDER>
>>>>
>>>> -Jian
>>>>
>>>> On Thursday, December 18, 2014 12:04:59 AM UTC-5, Sami Dubey wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Yes the content of text placeholder was changed by .NET.
>>>>> Yes we are able to see changed content in the 'edit via form' , not in
>>>>> page preview.
>>>>> Then manually if we press 'OK' it appears on the page preview.
>>>>>
>>>>> As you explained about caching, can you please help us on the clearing
>>>>> the text placeholder caching or any mechanism to save/ok the content for
>>>>> text placeholder.
>>>>> Code Snippet below:
>>>>> ==============================================================
>>>>>
>>>>> var pageGuid = new Guid(pageGUID);
>>>>>
>>>>> var newpage = project.Pages.GetByGuid(pageGuid,
>>>>> project.LanguageVariants.Current);
>>>>>
>>>>> var elementGuid = new Guid(elementGUIDArray[count]);
>>>>>
>>>>> count++;
>>>>>
>>>>> newpage.ResetToDraft();
>>>>>
>>>>> string text = project.GetTextContent(elementGuid,
>>>>> project.LanguageVariants.Current, "TextHtml");
>>>>>
>>>>> text = text.Replace("Recent", "Reciiient");
>>>>>
>>>>> //text placeholder content are getting changed in below
>>>>> code
>>>>>
>>>>> project.SetTextContent(elementGuid,
>>>>> project.LanguageVariants.Current, "TextHtml", text);
>>>>>
>>>>> newpage.Release();
>>>>>
>>>>> var publish = newpage.CreatePublishJob();
>>>>>
>>>>> publish.ProjectVariants = project.ProjectVariants;
>>>>>
>>>>> publish.LanguageVariants = project.LanguageVariants;
>>>>>
>>>>> publish.IsPublishingAllFollowingPages = true;
>>>>>
>>>>> publish.IsPublishingRelatedPages = true;
>>>>>
>>>>> publish.RunAsync();
>>>>>
>>>>>
>>>>> =========================================================================
>>>>> Thanks in Advance,
>>>>> With Regards
>>>>> Samridhi Dubey
>>>>> On Thursday, December 18, 2014 9:46:45 AM UTC+5:30, Jian Huang wrote:
>>>>>
>>>>>> Hi Sami,
>>>>>>
>>>>>> I am a little confused.
>>>>>>
>>>>>> If the content of text placeholder was changed by the .NET RQL, did
>>>>>> the changed content display in page preview? Did the changed content
>>>>>> display in edit via form?
>>>>>>
>>>>>> If no in page preview, but yes in edit via form, then that means the
>>>>>> 3rd party implementation saved the content correctly, However, it is
>>>>>> your
>>>>>> implementation on the template code that prevents update of the cache.
>>>>>>
>>>>>> Then again, manually editing the content via form refreshes cache, so
>>>>>> I can assume the template code might be correct, but only 70% sure.
>>>>>>
>>>>>> The ability to see the snippet of code that is responsible for
>>>>>> displayed the text content will help to answer a lot of questions.
>>>>>>
>>>>>> -Jian
>>>>>>
>>>>>> On Wednesday, December 17, 2014 11:05:16 PM UTC-5, Sami Dubey wrote:
>>>>>>>
>>>>>>> Sorry couldn't get you for the code line....
>>>>>>> We are just trying to change the content of text placeholder and
>>>>>>> publish the same...where we are able to change the content using server
>>>>>>> manager's set method..... also we are able to release the page.
>>>>>>>
>>>>>>> It is not publishing the content we changed for text placeholder,
>>>>>>> however we could see our changed content in management server.
>>>>>>>
>>>>>>> If we open the same content using 'Edit element via form' snd then
>>>>>>> 'ok' . It is appearing in page preview as well as publishes the same.
>>>>>>>
>>>>>>> We are unable to find the method to save or ok the changed content
>>>>>>> of text placeholder.
>>>>>>
>>>>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "RedDot CMS Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/reddot-cms-users/vSRKTK98ds0/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> reddot-cms-use...@googlegroups.com <javascript:>.
> To post to this group, send email to reddot-c...@googlegroups.com
> <javascript:>.
> Visit this group at http://groups.google.com/group/reddot-cms-users.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
--
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 reddot-cms-users+unsubscr...@googlegroups.com.
To post to this group, send email to reddot-cms-users@googlegroups.com.
Visit this group at http://groups.google.com/group/reddot-cms-users.
For more options, visit https://groups.google.com/d/optout.
