• Li-An

    (@li-an)


    I hesitate to put a one star rate as the plugin won’t work entirely on my configuration.

    First, the importation from All in One SEO data did not work. Developer contacted me and I accepted to open an admin account for him (something you should never do!) and FTP account (very bad idea!). He found that Ninja Firewall blocked the import (I was too lazy to make the test correctly). OK.

    Second: I discovered that the sitemap did not work. I installed the plugin on a test site (no other plugin and default theme) and same problem. I have a bunch of different sitemap solutions on my different WP installations and it is the first time I meet the problem. The answer from the developer did not satisfy me so I decided te stop wasting my time to debug something I consider not mature.

    It’s too bad as I like very much the philosophy of the plugin and basic functions work correctly.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Anh Tran

    (@rilwis)

    Hi @li-an,

    I’m sorry about the issues you had with the plugin and truly appreciate your feedback. I also talked with my developer to know what real problem is. Please let me give some details on them, so you can understand more about them.

    1. Regrading the migration from All In One SEO, we couldn’t replicate the errors on our site after many tries. We know asking for access is not a good way to solve this. Perhaps we could do better by asking your site info in the Health Check report in WordPress admin. After checking the site, we found the security plugin (Ninja Firewall) does some check on the PHP session, which we use to run the migration. We were able to fix that and the fix will be available in the next version. You can check to verify this.

    2. Regarding the sitemap, Slim SEO generates sitemap dynamically, which means there’s no real, physical sitemap file in the root folder of your website. Instead, it creates a link sitemap.xml and use it to show the sitemap. It’s similar to how WordPress create URL for pages and posts.

    However, if there’s a real, physical sitemap file in the root folder, WordPress will bypass the rewrite rule and serve the physical file instead (it’s how WordPress serve images and other static files). That’s the problem you saw on your test site (but not on your live site). And it happens not only with Slim SEO, but with all plugins. When we move the physical file to a sitemap-backup folder, to force WordPress to use the dynamic sitemap, then it works again.

    I understand these things are too technical that you might not be interested in. I’m just doing my best explaining them, so you can understand what we do.

    Hope you understand.

    Thank you,
    Anh

    Thread Starter Li-An

    (@li-an)

    I went to SEOPress?:?same sitemap concept and no problem.

    Plugin Author Anh Tran

    (@rilwis)

    Hi @li-an,

    I created a video with more details on the issue https://www.loom.com/share/527374693a6e4d3b9f9d5011a5593c61, and you’ll see in both Slim SEO and SEOPress, if there’s a physical sitemap file (sitemaps.xml for SEOPress and sitemap.xml for Slim SEO – note the file names are different), then the problem always occurs.

    Hope you understand.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Too much problems’ is closed to new replies.