auraleclipse

@tejwanihemant Apologies for my delay in responding – I am currently out of country. Thank you for your explanation of what occurred in the recent update. My use case is more or less the same as what @briancurtis has described, where in my case, I’ve been using Private status templates in Published status pages. I was doing this strictly to avoid the templates being directly accessible or indexed by search engines, as they historically have been showing up in sitemap.xml if in Published status.

I’ll go back to 1.2.12 and try setting all of the templates to Published status when I’m back home this weekend and ensure they’re no longer directly accessible or showing up in sitemap.xml.

Thanks @tejwanihemant for your efforts in maintaining the plugin and @briancurtis for sharing your input and experiences as well. I tend to agree this change should probably have been identified and documented as being potentially breaking. Those eagle-eyed among us who saw the improperly indexed templates and have been using the plugin for as long as we have would likely have been using this same workaround to achieve the desired outcome of this bug fix. I suppose I didn’t know better at the time that setting the templates to Private wasn’t just part of the typical use of the plugin!