I have my DEBUG turned on in my wp-config.php
on my dev environment and I’m getting this notice twice at the very top of every single page, front end and back end.
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the "simple-sitemap" domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114
My wp-config.php
settings:
if ( ! defined( 'WP_DEBUG' ) ) {
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true );
error_reporting(E_NOTICE);
}
WP Core is up to date, and deactivating the Simple Sitemap plug does remove the notice.
]]>I noticed a wp_options entry “fs_accounts” that is large in size and auto-loaded. Is this generated by the plug-in and is it necessary? If it is necessary, does it need to be auto-loaded?
]]>I deleted this plugin to troubleshoot issues on this site. The problem shown in the link (look at the bottom of the page) is gone on some pages, and on other pages, all pages, even unused pages that are set to private, are showing. I flushed the server’s cache, but I am still having issues. The code of the page still shows <div class=”ssmp simple-site-map”> then the full list of pages in the theme. Can you please assist?
]]>Since updating to WordPress 6.7 we’ve been getting the following notice in our development environment:
PHP Notice:? Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>simple-sitemap</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114;
Hi,
We installed the Simple Sitemap plugin and created the page, adding the following shortcode:
[simple-sitemap exclude='6']
The sitemap displayed all pages, but the expected exclusion of certain pages did not occur.
Could you kindly suggest a solution?
]]>The plugin’s XML sitemap isn’t updating after I publish new posts. I tried clearing the cache, but it still shows the old sitemap. Is there a manual way to regenerate it?
]]>Hi Everyone,
I am trying to create a user-friendly sitemap page but am finding it more difficult than it needs to be. On this page I am using three short codes:
[simple-sitemap exclude=”5, 104, 173, 2087, 2085, 2410, 176, 30040, 32326, 32168, 36186″]
This is my primary navigation. When I use the simple-sitemap-menu code I get the high level pages but cannot get the child pages to appear. When I use this version I cannot get them to appear in the order of my primary navigation.
[simple-sitemap-group taxonomy=”category” exclude_terms=”Where We’re Headed, Lifestyle”]
These are my posts. I want to show all my posts by the different categories they appear under. Unfortunately based on the way I’ve tagged the post two high level tags are appearing which is creating redundancy. I need to remove Lifestyle and Where We’re Headed. In addition I cannot get the categories to appear in the order that they are laid out in the primary navigation
[simple-sitemap-menu menu=”3″] This is my footer
I submitted a support ticket but have not heard anything back, so not sure it is supported. Which is frustrating because I just paid for the Pro level support. Part of me wants to build this page with section heads (h2 titles) then insert targeted shortcodes for content that appears in that section. Alot more work and more complexity but I feel like if I stick with this plugin I will have to consider that direction. At this point, if there is not an easy fix to what should be a standard approach to building a sitemap I am open to switching to another app if there is one better than this one.
Thank you for your patience, understanding and suppport.
John
]]>When i try to add the [simple-sitemap] on the text editor it shows Error Loading Block. The response is not a valid JSON response but when i add the simple group sitemap, it works just fine.
Thank you.
]]>If you are logged in the sitemap shows private pages. I find this very confusing and tried to get rid of these pages for quite a while (visibility=”true”) until i found out that they are shown only for me.
Is there a reason that they are shown for logged in users? I mean how can you test if something works if it doesn’t when logged in?
]]>The “Sorry, no … found” text is currently untranslatable.
Hi,
I can’t figure out how to change selected Sitemap Tab background color.
Can you please advise me.
Cheers,
Iztok
Started getting this error today and had to disable this plugin to be able to edit posts: “editor has encountered unexpected error”
]]>Purchase Premium version (via website) – DID NOT receive any confirmation, plugin files, license info or anytime at all.
My client and myself have reached out to support via the our website and your website and have received no response.
Please reach out to me here so we can resolve this, or send us the premium plugin info, or issue them a refund ASAP.
Thank you.
]]>The plugin breaks when we update WP 6.4.1. The site map previously created still shows on the front end but the blocks are broken in the admin page editor. They say the plugin is not compatible with an install button but the install button just errors out.
]]>Hi!
After PHP upgrade to PHP8.2 plugin throws a lot of “PHP Deprecated: Creation of dynamic property” warning.
Nothing breaks but would be good to fix it
Thanks!
]]>Wordfence is reporting a Vulnerability. Please see below for details.
Is the author aware, and working on a patch? We have no choice but to disable the plugin until there is a patch. Author PLEASE acknowledge, so we know whats going on. Thank you
]]>Hi, I noticed that Wordfence has detected a security vulnerability with Simple Sitemap:
https://www.wordfence.com/threat-intel/vulnerabilities/detail/freemius-sdk-259-reflected-cross-site-scripting-via-fs-request-get
Is this accurate? If so, do you plan to patch it?
Thanks!
Hello,
Any idea why Simple Sitemap is only showing pages, not published posts?
*edit* shortcodes below used that has solved.
[simple-sitemap]
[simple-sitemap-group]
However, I cannot exclude certain pages. I have added exclude=’279,278,277,8452,280674′ to the shortcode but that no longer works.
]]>Hello,
I have an issue with the plugin consuming almost 1GB memory to generate the sitemap page. I was thinkig if it’s possible to add some pagination to it?
Thank you,
]]>Wanted to just find out if there is an option to adjust any of the HTML created by the Simple Sitemap plugin. I’m interested in adding the hyperlinks or <a> tags around the list element or <li> tags. Have not been able to find any way to make that change.
Any help is greatly appreciated! Thank you!
]]>I have updated the PHP version from 7.4 to 8.0 and It is showing a fatal error
Error:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in wp-content/plugins/simple-sitemap-pro/api/classes/upgrade.php:83 Stack trace: #0 wp-includes/class-wp-hook.php(308): WPGO_Plugins\Plugin_Framework\Upgrade_FW->upgrade_routine(”) #1 wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #2 wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 wp-settings.php(480): do_action(‘plugins_loaded’) #4 wp-config.php(97): require_once(‘wp-set…’) #5 wp-load.php(50): require_once(‘wp-con…’) #6 wp-admin/admin.php(34): require_once(‘wp-loa…’) #7 wp-admin/plugins.php(10): require_once(‘wp-adm…’) #8 {main} thrown in wp-content/plugins/simple-sitemap-pro/api/classes/upgrade.php on line 83
Hello,
Is it possible to exclude my site’s events from the sitemap?
Thank you
]]>Is the exclude attribute no longer supported?
This is my shortcode, is there an error here?
[simple-sitemap types=’page’ show_label=’false’ exclude=’92,368′]
The title says it all, but I’ll elaborate.
I’d like to list all the posts from the website, except for the ones from a certain category.
Can I exclude posts from a certain category from showing up?
First I set up my html sitemap using the Gutenberg blocks, but sitemap would display the list of posts, the list of pages, then the same lists of posts and pages again. I was using the group-block for Posts, and the simple-block for pages. When checking in Preview it all looked normal, but once Published, everything doubled.
Next, I trashed and permanently deleted that page and started over using the short codes. [simple-sitemap-group type=’post’] & [simple-sitemap types=’page’].
Once again, it looked fine in Preview, but once published it double up again.
]]>Hi, I have used this plugin and integrated it on my https://www.guru.com/blog/html-sitemap/ page. Sometimes it’s loading properly but sometimes it’s throwing “HTTP ERROR 500” error.
Can you please tell me the reason for it?
]]>Hello,
I checked the sitemap today after I added it yesterday and it removed the links, even though the option to “Display sitemap links” is checked in the editor.
Also when trying to switch to another grouping method, like tags it doesn’t change the sitemap.
Thanks
]]>FYI this plugin conflicts with the Divi them and causes a timeout on the builder. This is with memory set to 4 times the recommended limit and plenty of resources.
]]>I run a multisite where all sites use the Divi theme, and see that this plugin is underlining everything with a link (headers, buttons, links, etc.)
I disabled on plugins on a staging site and I can see that this plugin is the only cause. Any recommendations on what I should do?
]]>Is there a way to include Archive pages for CPT’s? On my example site, I have a CPT for jiu-jitsu-programs. The individual programs pages are listed under the CPT name, but I’d also like to include the actual archive page. Is this possible?
]]>