Support Forum

SP Google XML plugin error

FO foxy7
foxy7
Member
Member since Dec 2013
67 posts
May 30, 2014 · 5:06 pm · Edited

I am having this error with the Google XML plugin, can you advise how to fix it?

“file: ullbet/public_html/wp-content/sp-resources/forum-plugins/google-sitemap/library/sp-google-sitemap-components.php

line: 12

function: sp_google_sitemap_do_add_index

Warning | Missing argument 1 for sp_google_sitemap_do_add_index(), called in /problem-with-post-edit-buttonome/skullbet/public_html/wp-content/sp-resources/forum-plugins/google-sitemap/sp-google-sitemap-plugin.php on line 113 and defined“

 

I just recently removed an admin in WP, unfortunately without attributing all content to another user. That resulted in a deleted page (which I could easily restore) and a deleted header. Not sure if that mistake could be related to this? Thanks for your help.

 

11-1.PNG22-1.PNG

error.PNG 11.PNG 22.PNG 11-1.PNG 22-1.PNG

3 Answers

New Answer
YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
May 31, 2014 · 3:06 am

I am not an expert on this so Steve may have some extra insight when he returns but basically the WordPress sitemap plugin is making the call to the SP plugin code and passing no value. So you may be correct in your assertion but I am not sure….

I do think it would be a good idea for us to trap the empty value condition whether it should happen or not so that at least we avoid putting out annoying warnings. And I will open a ticket on that score.

By the way – I do realise you are trying to help but there is no need to paste images of code fragments. We do have all of the code of course and we will always look at the actual source in our code editors in situations like this. And it will save you time and effort as well!

FO foxy7
foxy7
Member
Member since Dec 2013
67 posts
May 31, 2014 · 4:13 am

OK, I will wait for Steve on this one. And thanks for the heads up regarding the unnecessary code pasting 😉 

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
May 31, 2014 · 2:18 pm

actually, this was reported a couple weeks ago by a user and already fixed… should be available when we release 5.5 and plugin updates tomorrow…