Title: auraleclipse's Replies | WordPress.org

---

# auraleclipse

  [  ](https://wordpress.org/support/users/auraleclipse/)

 *   [Profile](https://wordpress.org/support/users/auraleclipse/)
 *   [Topics Started](https://wordpress.org/support/users/auraleclipse/topics/)
 *   [Replies Created](https://wordpress.org/support/users/auraleclipse/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/auraleclipse/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/auraleclipse/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/auraleclipse/engagements/)
 *   [Favorites](https://wordpress.org/support/users/auraleclipse/favorites/)

 Search replies:

## Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Dynific Addons for Elementor (formerly AnyWhere Elementor)] Shortcode insertion stopped working after update to 1.2.12](https://wordpress.org/support/topic/shortcode-insertion-stopped-working-after-update-to-1-2-12/)
 *  Thread Starter [auraleclipse](https://wordpress.org/support/users/auraleclipse/)
 * (@auraleclipse)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/shortcode-insertion-stopped-working-after-update-to-1-2-12/#post-18185618)
 * [@tejwanihemant](https://wordpress.org/support/users/tejwanihemant/), I have 
   upgraded the plugin back to 1.2.12, set all of my AE templates to Published status,
   and tested. All templates appear to be appearing in the pages as expected, however
   the published template entries still end up in sitemap.xml in format `https://{
   domain}/?ae_global_templates={ae_template_name}`. Despite this, they are each
   301 redirecting to the homepage, so I’d consider that an acceptable tradeoff.
   I’m marking this issue as resolved, thank you.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Dynific Addons for Elementor (formerly AnyWhere Elementor)] Shortcode insertion stopped working after update to 1.2.12](https://wordpress.org/support/topic/shortcode-insertion-stopped-working-after-update-to-1-2-12/)
 *  Thread Starter [auraleclipse](https://wordpress.org/support/users/auraleclipse/)
 * (@auraleclipse)
 * [1 year, 7 months ago](https://wordpress.org/support/topic/shortcode-insertion-stopped-working-after-update-to-1-2-12/#post-18180943)
 * [@tejwanihemant](https://wordpress.org/support/users/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](https://wordpress.org/support/users/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](https://wordpress.org/support/users/tejwanihemant/) for
   your efforts in maintaining the plugin and [@briancurtis](https://wordpress.org/support/users/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!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Easy Updates Manager] Latest update to version 9.0.5 causes fatal error in dashboard](https://wordpress.org/support/topic/latest-update-to-version-9-0-5-causes-fatal-error-in-dashboard/)
 *  Thread Starter [auraleclipse](https://wordpress.org/support/users/auraleclipse/)
 * (@auraleclipse)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/latest-update-to-version-9-0-5-causes-fatal-error-in-dashboard/#post-13234343)
 * [@davidanderson](https://wordpress.org/support/users/davidanderson/) , thanks
   for the quick fix – update was also successful in resolving the issue on my end.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Easy Updates Manager] Critical error](https://wordpress.org/support/topic/critical-error-99/)
 *  [auraleclipse](https://wordpress.org/support/users/auraleclipse/)
 * (@auraleclipse)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-99/#post-13234115)
 * [@panosakris](https://wordpress.org/support/users/panosakris/), temporary fix
   was just to back up the offending script and save it as an empty file:
 * /wp-content/plugins/stops-core-theme-and-plugin-updates/templates/notices/thanks-
   for-using-main-dash.php
 * `cp thanks-for-using-main-dash.php thanks-for-using-main-dash.php.bak && echo""
   > thanks-for-using-main-dash.php`
 * The dashboard and plugin configuration page works as expected for me afterwards.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Easy Updates Manager] Latest update to version 9.0.5 causes fatal error in dashboard](https://wordpress.org/support/topic/latest-update-to-version-9-0-5-causes-fatal-error-in-dashboard/)
 *  Thread Starter [auraleclipse](https://wordpress.org/support/users/auraleclipse/)
 * (@auraleclipse)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/latest-update-to-version-9-0-5-causes-fatal-error-in-dashboard/#post-13234109)
 * Temporary fix was just to back up the offending script and save it as an empty
   file:
 * /wp-content/plugins/stops-core-theme-and-plugin-updates/templates/notices/thanks-
   for-using-main-dash.php
 * `cp thanks-for-using-main-dash.php thanks-for-using-main-dash.php.bak && echo""
   > thanks-for-using-main-dash.php`

Viewing 5 replies - 1 through 5 (of 5 total)