SitemapXML v.2

Today I got this, for unknown reasons

Ping Yahoo!

http://search.yahooapis.com/SiteExpl...temapindex.xml Update notification has successfully submitted.


I have already entered the fix published by a_berezin.
However, this Yahoo notification was previous to that, so unrelated.
Anyway, my files were never compressed, so the fix wouldn't affect the ping.
Actually, it is quite easy to understand the fix:
$pattern = '/^' . $this->filename . '.*(\.xml' . (SITEMAPXML_COMPRESS == 'true' ? '|\.xml\.gz' : '') . ')$/';
Basically this is saying: if sitemap files are compressed, then extension .gz.
Before it was the opposite.
I also have to note that I hard-coded the variable %s, I typed the whole URL there, only for Yahoo, in the Config for Sitemap XML.
That was not fixing it either, so I will test in the following days with the variable back.
Bottom line, I have no idea why this is/was happening, I posted to Yahoo dev forums to no avail.
Maybe the new authentication process solved it?
Maybe Yahoo changed something on their end?
Mystery...

Quote:

---

Originally Posted by ckosloff

You are right, I was in a hurry, will post in a moment.
HOWEVER...the damn thing is back where it was.
Cron reported same error.
Anybody else having problems with Yahoo??

https://siteexplorer.search.yahoo.com/mysites
Go here and click on the site you wish to authenticate.
You need to create an account with Yahoo first.

---

Yes I have the same error in my sitemapxml v.2 ping build notification pop up.
No idea why it started now. It was working ok 3 days ago and broke around the same time as yours, so I guess it is likely to be a Yahoo issue.:unsure:

Regarding this pesky Yahoo thing, I have been giving it some thought.
First, let me say that it is happy for me now, and I have the %s back in there.
So, whether you use the variable or not should not make a difference.
A 403 error means the server is denying access, it is basically saying "forbidden", therefore a full authentication process should fix this, since they want to verify that the owner of the site is pinging and not someone else, possibly to prevent DoS attacks.
Also, you do have to update your sitemap before pinging.
If manually you hit repeatedly step 2 in Tools -> Sitemap XML, Yahoo will throw the damn error, the other SE will not complain.
But, if you hit step 1 first and then step 2, it will be happy.
I have my cron set to do this automatically, according to instructions, so it is happy now.
I think I got the error back because that day I was testing the thing a lot, and missing step 1.
I think Yahoo got burned since the last DoS attack and are now overly cautious.
For the moment, I would say that the fix is authentication + updating.
Hopefully.

Hi ckosloff,
Excellent explanation!

anyone can help? I installed it, but can not see Admin->Tools>Google XML Sitemap..................? how to fix it ?

Quote:

---

Originally Posted by Junzilang

anyone can help? I installed it, but can not see Admin->Tools>Google XML Sitemap..................? how to fix it ?

---

And I have copied all files to correct position, tried 2 times, and ran the .sql file, still can not see it. hope some could tell me how to fix it? thank u very much

Quote:

---

Originally Posted by Junzilang

And I have copied all files to correct position, tried 2 times, and ran the .sql file, still can not see it. hope some could tell me how to fix it? thank u very much

---

I have fixed this problem, due to I changed my admin folder name, so the files did not copy to the corresponding position...........so just need copy the files to my currently "xxxadminxxx""

Quote:

---

Originally Posted by ckosloff

Regarding this pesky Yahoo thing, I have been giving it some thought.
First, let me say that it is happy for me now, and I have the %s back in there.
So, whether you use the variable or not should not make a difference.
A 403 error means the server is denying access, it is basically saying "forbidden", therefore a full authentication process should fix this, since they want to verify that the owner of the site is pinging and not someone else, possibly to prevent DoS attacks.
Also, you do have to update your sitemap before pinging.
If manually you hit repeatedly step 2 in Tools -> Sitemap XML, Yahoo will throw the damn error, the other SE will not complain.
But, if you hit step 1 first and then step 2, it will be happy.
I have my cron set to do this automatically, according to instructions, so it is happy now.
I think I got the error back because that day I was testing the thing a lot, and missing step 1.
I think Yahoo got burned since the last DoS attack and are now overly cautious.
For the moment, I would say that the fix is authentication + updating.
Hopefully.

---

Hi, ckosloff

Thanks for your useful explanation! I would like to remember:
But, if you hit step 1 first and then step 2, it will be happy.
I have my cron set to do this automatically, according to instructions, so it is happy now.

Nice job,

hello, my problem is:
even setting this option to false, Generate language_id for default language, i still get this in my links
http://casasnossasenhoradosprazeres....ro-25-cm-p-526/language/br

what i'm missing?

Thank you very much

The problem is resolved now, just needed a little time to change.

Thank you