Legacy Add Hook in class_sitemap.php

[neounix]

Hey!

Do you mind to add a hook in class_sitemap.php after this code:

        /**
        * Default name for sitemap files, which is prepended by the sitemap file count
        *
        * @var  string
        */
        private $sitemap_filename_prefix = 'dbseo_sitemap_';

        const FLAG_PING_GOOGLE      = 0x1;
        const FLAG_PING_LIVE_SEARCH = 0x2;
        const FLAG_PING_YAHOO       = 0x4;
        const FLAG_PING_ASK         = 0x8;
        const FLAG_PING_MOREOVER    = 0x10;
        const FLAG_PING_BING            = 0x20;

        /**
        * Array of search engine urls' for sitemap call back, populated with defaults from options
        *
        * @var  array
        */
        public $search_engines = array(
                self::FLAG_PING_GOOGLE      => 'http://www.google.com/webmasters/sitemaps/ping?sitemap=',
                //self::FLAG_PING_LIVE_SEARCH => 'http://webmaster.live.com/ping.aspx?siteMap=',
                self::FLAG_PING_YAHOO       => 'http://search.yahooapis.com/SiteExplorerService/V1/ping?sitemap=',
                self::FLAG_PING_ASK         => 'http://submissions.ask.com/ping?sitemap=',
                self::FLAG_PING_MOREOVER    => 'http://api.moreover.com/ping?u=',
                self::FLAG_PING_BING            => 'http://www.bing.com/ping?sitemap=',
        );

So we can also override the $sitemap_filename_prefix = 'dbseo_sitemap_' and the $sitemap_index_filename = 'dbseo_sitemap_index' variables to help us with our multiple sitemap code?

Also, that hook location could be used to add future search engines to ping as well

Thanks.

 

[Fillip H.]

I've added dbtech_dbseo_sitemap_generate_start in DBSEO_SiteMap::__construct for tonight's Beta 10.

You cannot have hooks inline in classes, but you should be able to access private variables within the __construct function.

 

[neounix]

Thanks again. I'll give it a try soon and see if it works.

I'm struggling to debug why, in two supposedly identical sites, our lightweight mobile style works in one and does not work in the other. The database is the same, the entire HTML directory is the same, the apache2 config files are the same... Hahaha.. It's (in theory) all the same, but our mobile style has stopped working on our main site.