Curtis, Both code will actually prevent pages with multiple connections being crawled multiple times, or even recursive publishing if one page is connected to another, and another is connected to one. It is highly recommended to have either code in place.
Should you require additional assistance, I can help here or you can reach out to OpenText Consulting Services. Best regards, -Jian On Monday, December 10, 2012 3:23:36 PM UTC-5, Curtis Kimball wrote: > > Ok so it never stopped the second publish? > > I guess I'll remove that code. > > - Curtis > Web Services Director > SNHU.edu > > On Dec 10, 2012, at 2:07 PM, "Jian Huang" <[email protected]<javascript:>> > wrote: > > No value since a better solution is found. I listed it there for 2 reasons > > 1. SEO, so people can search and find it without knowledge of a newer > solution. > 2. Context, can't really introduce a new solution without explaining the > history and theory behind things. > > -Jian > > On Monday, December 10, 2012 12:29:02 PM UTC-5, Curtis Kimball wrote: >> >> I saw that, but thought it was only relevant to the "All version >> Compatible Solution". >> >> So, what is the value of changing the "islink" in version 7.5? >> >> curtis >> >> From: Jian Huang <[email protected]> >> Reply-To: "[email protected]" <[email protected]> >> Date: Monday, December 10, 2012 11:58 AM >> To: "[email protected]" <[email protected]> >> Subject: Re: publish issues >> >> Oh, forgot to mention, at the bottom of the article, though it is easy to >> miss, but it says >> >> *Page 1 and page 2 still get published according to different >> publication packages, but links generated always point to the pages' main >> link * >> >> -Jian >> >> On Monday, December 10, 2012 11:55:06 AM UTC-5, Jian Huang wrote: >>> >>> Hi Curtis, >>> >>> If the page only contains link produced with either solutions, then the >>> follow pages won't be crawled. Please note that the non-fixed links can't >>> even appear in HTML comments or preexecution comments, CMS still pick those >>> up and crawl them. >>> >>> Now, if you publish any pages that are connected to multiple locations, >>> then the pages will get publish multiple times. >>> >>> There is a fix to it. For those lists that contains pages with multiple >>> connections, attached a publication package that publish them to a folder, >>> I usually name it, norobot, then configure your indexer not to crawl this >>> folder. >>> >>> -Jian >>> >>> On Monday, December 10, 2012 11:45:37 AM UTC-5, Curtis Kimball wrote: >>>> >>>> The rendertag works now that the flag was changed. >>>> The current issue is that the pages still publish to the route. >>>> This is an issue mainly because it could be indexed as duplicate content >>>> Also that this results in different pages being published to the same >>>> URL in the root. >>>> >>>> The information on your blog led me to believe that changing the islink >>>> would trick CMS into thinking the following pages are references, hence >>>> NOT to crawl and publish following pages. >>>> >>>> >>>> >>>> From: Jian Huang <[email protected]> >>>> Reply-To: "[email protected]" <[email protected]> >>>> Date: Monday, December 10, 2012 10:52 AM >>>> To: "[email protected]" <[email protected]> >>>> Subject: Re: publish issues >>>> >>>> Hi Curtis, >>>> >>>> I believe the rendertag code method was not rendering was because flag >>>> value in RDserver.ini was not set to 1024 or 1248 and navigation manager >>>> was not activate in project settings. It was working once activated. >>>> >>>> Yes, the rendertag method only changes the links to mainlink, would not >>>> prevent the following pages from publishing to other locations. Likewise, >>>> so does the islink=2 to islink=10 method. >>>> >>>> Please elaborate on "it wasn't working". Is it not producing the link >>>> correctly or it produced the link, but page still publishes to multiple >>>> locations? >>>> >>>> On Monday, December 10, 2012 9:16:45 AM UTC-5, Curtis Kimball wrote: >>>>> >>>>> Actually, since we're using version 7.5, the "obsolete" solution >>>>> should work and that is supposed to not publish the following pages. >>>>> >>>>> *Edit the content class of "RSS Listing", use preexecution to replace >>>>> islink=2 with islink=10 to trick CMS into thinking the following pages >>>>> are >>>>> references, hence not to crawl and publish following pages. * >>>>> >>>>> Just trying to figure out why it's not working. >>>>> >>>>> curtis >>>>> From: Nathan Palmer <[email protected]> >>>>> Reply-To: "[email protected]" <[email protected] >>>>> > >>>>> Date: Friday, December 7, 2012 1:44 PM >>>>> To: "[email protected]" <[email protected]> >>>>> Subject: Re: publish issues >>>>> >>>>> Jian's fix doesn't prevent the pages from publishing out in multiple >>>>> places, it only prevents them from having any links reference them. So if >>>>> you've done it properly you'll still see those pages publish in multiple >>>>> places but all the links on the site should point to the same location >>>>> (the >>>>> main link). >>>>> >>>>> On Fri, Dec 7, 2012 at 12:53 PM, Kimball, Curtis <[email protected]>wrote: >>>>> >>>>>> Turns out that navigation manager has to be turned on and ours was >>>>>> not. >>>>>> That resolved the rendertag output issue. >>>>>> >>>>>> We are still having pages publish out twice despite being >>>>>> "referenced" and not connected. >>>>>> >>>>>> Still trying to identify where and why. >>>>>> >>>>>> Curtis >>>>>> >>>>>> From: Bob Foster <[email protected]> >>>>>> Reply-To: "[email protected]" < >>>>>> [email protected]> >>>>>> Date: Friday, December 7, 2012 11:51 AM >>>>>> To: "[email protected]" <[email protected]> >>>>>> Cc: "[email protected]" <[email protected]> >>>>>> Subject: Re: publish issues >>>>>> >>>>>> Curtis, >>>>>> >>>>>> Let us take a look at the code for this. >>>>>> >>>>>> Rob >>>>>> >>>>>> Sent from my iPad >>>>>> >>>>>> On Dec 5, 2012, at 12:47 PM, "Kimball, Curtis" <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Thanks >>>>>> We found something similar and have been trying to implement what >>>>>> Jian has on the blog. >>>>>> Fortunately, we are still on version 7.5 so we are also implementing >>>>>> the code to change the link to be viewed as a reference. >>>>>> >>>>>> The problem we are having currently is the rendertag code is >>>>>> outputting code as text and not inserting the url as needed: >>>>>> So this is the published code: >>>>>> >>>>>> <li>linkgoeshere<ahref="<%!! >>>>>> Context:Pages.GetPage(Guid:AB7A9B75374941D3B578150B434B0D85).GetUrl(Bool:True) >>>>>> >>>>>> !!%>"><spanclass="relatedLink">Accounting / Auditing (MS)</span></a> >>>>>> >>>>>> >>>>>> Anyone know what I'm doing wrong? >>>>>> >>>>>> Haven't done anything with rendertags before. >>>>>> >>>>>> >>>>>> Curtis >>>>>> From: Nathan Palmer <[email protected]> >>>>>> Reply-To: "[email protected]" < >>>>>> [email protected]> >>>>>> Date: Wednesday, December 5, 2012 10:50 AM >>>>>> To: "[email protected]" <[email protected]> >>>>>> Subject: Re: publish issues >>>>>> >>>>>> Confirmed, and it's the bane of implementations everywhere. However, >>>>>> there are a few well-accepted practices you can follow to avoid problems: >>>>>> >>>>>> 1. Never use "Connect Existing Page" for links. Always use >>>>>> "Reference Page". >>>>>> 2. Take advantage of Jian Huang's wonderful plugin to find pages >>>>>> that are connected in multiple locations so you can fix them: >>>>>> >>>>>> http://simplyreddot.blogspot.com/2012/03/check-multiple-page-connections.html >>>>>> 3. For keyword lists (where pages have to be connected rather >>>>>> than referenced) use render tags to generate the link URL so it goes >>>>>> to the >>>>>> main link. See >>>>>> http://simplyreddot.blogspot.com/2012/01/duplicate-pages.html >>>>>> >>>>>> Hope this helps. >>>>>> >>>>>> On Wed, Dec 5, 2012 at 10:39 AM, Joel Kinzel <[email protected]>wrote: >>>>>> >>>>>>> I think we will need more information. What version are you running? >>>>>>> Are you publishing locally or via FTP? What settings are you using (all >>>>>>> following/all related checked?)? >>>>>>> >>>>>>> >>>>>>> On Tuesday, December 4, 2012 2:38:23 PM UTC-6, Curtis Kimball wrote: >>>>>>> >>>>>>>> Can anyone confirm that publishing will NOT only follow the >>>>>>>> connection of the main link as described, but will actually publish >>>>>>>> multiple times based on every connection throughout the site. >>>>>>>> >>>>>>>> Reddot support says they don't have me in their system despite >>>>>>>> being a customer for 7 years. >>>>>>>> >>>>>>>> >>>>>>>> >Original Message >>>>>>>> >>>>>>>> From: [email protected] >>>>>>>> >>>>>>>> Sent: 12/04/2012 13:59:38 >>>>>>>> >>>>>>>> To: [email protected] >>>>>>>> >>>>>>>> Subject: publishing from multiple lists >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I have a page in a project that I want to publish to a specific >>>>>>>> directory. >>>>>>>> >>>>>>>> http://webdevsrv.snhu.edu/**online-degrees/graduate-** >>>>>>>> degrees/English-and-Creative-**Writing-MA.asp<http://webdevsrv.snhu.edu/online-degrees/graduate-degrees/English-and-Creative-Writing-MA.asp> >>>>>>>> >>>>>>>> We created the publication package, made sure that was the main >>>>>>>> link, and got the file to publish where we want it. >>>>>>>> >>>>>>>> The problem is that that same page is connected to other lists as >>>>>>>> well. (like the navigation on the left side) >>>>>>>> >>>>>>>> http://webdevsrv.snhu.edu/**online-degrees/graduate-** >>>>>>>> degrees/english-and-creative-**writing-MA-online/English-and-** >>>>>>>> Creative-Writing-MA.asp<http://webdevsrv.snhu.edu/online-degrees/graduate-degrees/english-and-creative-writing-MA-online/English-and-Creative-Writing-MA.asp> >>>>>>>> >>>>>>>> Those other lists have different publication packages on them. (and >>>>>>>> they need to be that way) >>>>>>>> >>>>>>>> I do NOT want the original page publishing to multiple paths. >>>>>>>> >>>>>>>> I thought that the publication would follow only the MAIN link. >>>>>>>> >>>>>>>> When I look at the page info it says that the pub path is correct. >>>>>>>> >>>>>>>> How do I stop the page from publishing with multiple paths? >>>>>>>> >>>>>>>> Curtis >>>>>>>> >>>>>>>> Please consider the environment before printing this e-mail. >>>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "RedDot CMS Users" group. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msg/reddot-cms-users/-/XwN1GlS2iLwJ. >>>>>>> >>>>>>> To post to this group, send email to [email protected]. >>>>>>> To unsubscribe from this group, send email to >>>>>>> [email protected]. >>>>>>> For more options, visit this group at >>>>>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>>>>> >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "RedDot CMS Users" group. >>>>>> To post to this group, send email to [email protected]. >>>>>> To unsubscribe from this group, send email to >>>>>> [email protected]. >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "RedDot CMS Users" group. >>>>>> To post to this group, send email to [email protected]. >>>>>> To unsubscribe from this group, send email to >>>>>> [email protected]. >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "RedDot CMS Users" group. >>>>>> To post to this group, send email to [email protected]. >>>>>> To unsubscribe from this group, send email to >>>>>> [email protected]. >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "RedDot CMS Users" group. >>>>>> To post to this group, send email to [email protected]. >>>>>> To unsubscribe from this group, send email to >>>>>> [email protected]. >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "RedDot CMS Users" group. >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to >>>>> [email protected]. >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "RedDot CMS Users" group. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msg/reddot-cms-users/-/Ckr6t7LHYOIJ. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "RedDot CMS Users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/reddot-cms-users/-/cndH16EJYaMJ. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/reddot-cms-users?hl=en. >> > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/reddot-cms-users/-/PMqKZRMrfnsJ. > To post to this group, send email to [email protected]<javascript:> > . > To unsubscribe from this group, send email to > [email protected] <javascript:>. > For more options, visit this group at > http://groups.google.com/group/reddot-cms-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/mI00RJlgn2MJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
