Dominik Kocuj

Hello.

Thank you for using the “Kocuj Sitemap” plugin.

During the update of the menus, posts and pages the cache is being created. It should be that way, because it make a sitemap the same as list of all articles in database.

I’ve looked at this process and found a bug. For some reason the process of creating the cache is made several times after clicking on “save” button. I’m not sure if this is the reason for your problems, but because it is definitely a bug, I will correct it and I will release a new plugin version as soon as possible (today or tomorrow). Maybe this fix will help in your case.

But maybe you can give me also an additional information. What WordPress version do you have? And please make sure if there is a problem only when “Kocuj Sitemap” plugin is enabled – and not when it is disabled.

Thank you! It’s working now.

Thank you for using the Kocuj Sitemap plugin and your review.

I’d like to fix that, however I don’t have your problems in administration panel after installing the Kocuj Sitemap plugin. Can you provide more information? You wrote that some JavaScript file cannot be loaded. Can you tell which one? Can you also say more information about what did you exactly do and what exactly happen and when?

I just don’t have any problems with the Kocuj Sitemap plugin in WordPress 4.2, so any more information will be helpful if there is some error on the Kocuj Sitemap plugin part.

Thank you for using this plugin. It’s good to read good words about it and having good reviews.

It’s really strange that there is always only Spanish language. The “Kocuj Sitemap” plugin was tested many times with and without qTranslate and there were no problems at all. So, I think, it can be some not typical problem and I have a few ideas and question which can help to find the answer or correct this. Please do this in the following order and after each point please check if it is worked correctly – if no, please do the next point from list.

1) Remove cache for “Kocuj Sitemap”. There is no option for do this, but saving options in settings for this plugin in administration panel is always regenerating the cache. So, please, click on the button “Save settings”.

2) Check in “Kocuj Sitemap” plugin settings in administration panel the tab “Multi-language plugin”, if option “Use qTranslate plugin” is checked. If it is not checked, please do it, and click on the button “Save settings”.

3) Remove cache manually by removing all files with “.dat” extension from directory “/wp-content/plugins/kocuj-sitemap/cache”. Then please refresh your website – not in administration panel, but in frontend.

I think that there are problems with cache, so one point from the above list should work. If not, please, let me know if you are using WordPress in multisite mode (MU – with sites network), or normal WordPress (no sites network).

The problem with cache can be when – for example – “qTranslate” plugin was installed AFTER “Kocuj Sitemap” plugin was installed and configured. It can happen because of generated cache – it will be generated without any translations. I think it is some bug to correct in the next version (I’m working on it).

Please, let me know if any of this was helpful.

As I wrote above “Kocuj Sitemap” plugin generates cache after changing options or any post or page in administration panel, so it will save all pages without excluding it by other plugins (which, usually, do not exclude anything in administration panel).

I do not planning to add integration with specific plugin for excluding pages. This will not change anything because excluding pages require many changes in “Kocuj Sitemap” plugin, so collaboration with another plugin is not necessary. I’m not planning to make “Kocuj Sitemap” plugin excluding posts feature compatible with some specific plugin, because there is no such reason. There will be in version 2.0 possibility to enable generating cache in frontend (not in administration panel), so it will add possibility to exclude pages by another plugin which will be used by “Kocuj Sitemap” plugin. However, it is still waiting to be released in 2.0 version.

I’ve checked it and it works. All warnings are gone.

Thank you.

I agree. For now I have the last 3.x.x version and I’m waiting for stable version, because current 4.x.x is not stable enough.

In hosting, where I have all my websites, files and directories in each domain and subdomain are treated like in the root (“/”) path. So, the ABSPATH = “/” is correct.

For example, in this hosting if I have a directory:
“/mywebsite”
and domain
“https://mywebsite.com”
which is set to this directory, then all directories and files in “/mywebsite” will be treated as if they are in the root directory, for example, URL
“https://mywebsite.com/something.php”
will execute script at
“/mywebsite/something.php”.
Furthermore, from script point of view the “/mywebsite” directory does not exists – all inside is treated like in root path (“/”).

So if you need this to generate some URL, I think it should be ok in this case. For example, URL:
“https://somedomain.com”.$abspath.”/something.php”
where $abspath is ABSPATH after trimming in your plugin (by eliminating “/”), will be ok in my case, because it will be:
“https://somedomain.com/something.php”
and it is correct URL.

This is how it works in my case.

I have the same error.

I’ve looked into the code of your plugin and I see that in file lib/icon-fonts/init.php you’re getting the ABSPATH and then you’re trimming it by removing the “/” characters. However, because I have the website in the main directory, I have the ABSPATH = “/”. So, when you remove this character and then you make a “strpos()” with this as the second parameter, the “strpos()” function will show these errors.

Warning: strpos(): Empty needle in /wp-content/plugins/better-wp-security/lib/icon-fonts/init.php on line 20

Warning: strpos(): Empty needle in /wp-content/plugins/better-wp-security/lib/icon-fonts/init.php on line 29

That’s some errors in administration panel which I have after updating your plugin. Installing it as new does not change anything.

I’ve looked into the code of your plugin and I see that in file lib/icon-fonts/init.php you’re getting the ABSPATH and then you’re trimming it by removing the “/” characters. However, because I have the website in the main directory, I have the ABSPATH = “/”. So, when you remove this character and then you make a “strpos()” with this as the second parameter, the “strpos()” function will show errors which I describe at the beginning of this post.

Can you correct this bug? Because – for now – your plugin cannot be used and I’m forced to stay with the older version.

Thank you for your interest in my plugin.

Excluding posts and pages require many changes to the plugin code. Because of this it takes some time to do this.

There is a 2.0 plugin version in development, so many new features will be available in this version. However, I can’t tell when exactly this version will be released. There are still much work to do with new features (for example, with excluding posts and pages) and some bugs.

You can check information about developing of this version on the project website – https://kocujsitemap.wpplugin.kocuj.pl (development tasks are available on: https://kocujsitemap.wpplugin.kocuj.pl/to-do-list ). When the date of release will be known to me, I will add information on that website, so it is the best place for being informed about the development status.

During my coding for the next version of “Kocuj Sitemap” plugin I’ve checked why there are problems with cooperation with “WP Hide Post” plugin. It’s look like that “WP Hide Post” plugin exclude posts only in frontend, not in administration panel. I understand why it is written in that way, but it has an unneeded effect of not working with cooperation with my plugin. “Kocuj Sitemap” generates cache after changing options or any post or page in administration panel, so it will save all pages without excluding it with “WP Hide Post” plugin. So there is almost nothing I can do with this (cache must be generate in administration panel), but it should be not a problem in the next version of “Kocuj Sitemap” because I will add a built-in feature with excluding posts or pages.

I just want to make it clear that these two plugins will rather not cooperate even with the next version of “Kocuj Sitemap” plugin.

Thank you for this idea. It’s not a problem to add this type of functionality, so I will add this to to-do list for the next version.

I didn’t use “Google XML Sitemap for qTranslate” – only its version without multilingualism, so I don’t know about this problem. Maybe they will help in their support forum?