Support » Plugin: LiteSpeed Cache » Crawler Exclude Custom Post Types Option Is Broken

  • Hello,

    I noticed that when I specify more than one CPT in the [Exclude Custom Post Types] field, it has no effect when I click on [Generate Crawler File]. It works fine when I only specify one, but when I add even one more the exclusions are not implemented (Even though they are still listed in the field). And yes, the [Custom Sitemap] field is blank.

    Thanks in advance!

    Jake

Viewing 9 replies - 1 through 9 (of 9 total)
  • FYI, here is my Litespeed report ID: LGCOXSQN.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Could you please compare the file /wp-content/plugins/litespeed-cache/var/crawlermap.data when generated from 1 exclude and multiple exclude ?

    Best regards,

    Hello,

    Sure! When there are NO exclusions listed in the [Exclude Custom Post Types] field, and I click [Generate Crawler File] under the Crawler tool, there are 1887 entries. For this example, here are the counts (According to crawlermap.data) for the CPTs we’ll be excluding:

    tribe_events (1,286 items)
    tribe_venue (1 item)

    When there is 1 exclusion listed in the [Exclude Custom Post Types] field (tribe_events), and I click [Generate Crawler File] under the Crawler tool, there are 600 entries. The tribe_events CPT is excluded.

    When there are 2 exclusions listed in the [Exclude Custom Post Types] field (tribe_events, and tribe_venue – each on their own line), and I click [Generate Crawler File] under the Crawler tool, there are 1887 entries. The tribe_events and tribe_venue CPTs are NOT excluded.

    Let me know if you need more info.

    Thanks!

    Jake

    • This reply was modified 5 months, 1 week ago by Jacob Hill.
    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I have managed to reproduce it , will check up with our developers

    Best regards,

    Excellent, thank you for the update!

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    After checked with developers.

    This will be fixed in v 3.0

    At this moment I do not have exact ETA yet but it should be released in near future.

    Best regards,

    Hello @qtwrk, just confirming this fix is still on track for 3.0? Thanks in advance!

    Hello @qtwrk, I’m hoping to see the issue fixed soon. Any update on 3.0? Thank you!

    @stanleylitespeed @qtwrk any update on this? Is there any workaround?

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.