Support » Plugin: Internal Link Juicer: SEO Auto Linker for WordPress » Only a third of marked pages receive links

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Internal Links

    (@internallinkjuicer)

    Can you please send us some additional screenshots of your plugin configurations – This will allow us to recreate the scenario you describe at our end and get to the bottom of it.

    Thread Starter adsim

    (@adsim)

    Plugin Author Internal Links

    (@internallinkjuicer)

    Thanks for providing the screenshots of your settings.

    We have tried to replicate the issue but we have not found any issues on our end. Would it be possible to give us more details on the issue (like what theme you are using, if there are any page builders installed, or if you are using a custom template for your custom post type)?

    Thread Starter adsim

    (@adsim)

    Sure. We use a custom build theme with several custom post types. No page builder.
    What I tried so far:
    1. Deactivating all plugins except Internal Link Juicer, Advanced Custom Fields and WPML (the last 2 because there are functions in the theme that rely on them)
    2. Changing the theme to a standard theme (TwentyOne)
    3. Change “$content = apply_filters(‘the_content’, get_the_content());” to “the_content;” inside the single template of the custom post type.
    4. Copied the text of a custom post type post which contains keywords inside a normal post, to see if the keywords are grabbed in a normal post
    5. Set up a dev enviroment at a different host

    Nothing changed something.

    What’s weird is that it is working on a third of the keywords.

    Plugin Author Internal Links

    (@internallinkjuicer)

    Ah I see, you are using ACF. Thanks for your detailed description.

    Can you confirm, that the parts that do not get linked, come from custom fields, generated by ACF (or is the content editor the standard WordPress editor of the “Glossar” type)?

    Thread Starter adsim

    (@adsim)

    I can confirm, that the parts do not get linked, come from the standard WordPress editor.
    The “Glossar” custom post type uses only the standard content editor of WordPress and the texts containing keywords to get linked are also coming exclusivly from the standard content editor of WordPress.
    The strange thing is, there are no “technical” differences I can see between the keywords that get linked and the keywords that don’t. They all come from the standard content editor. No custom fields, no shortcodes, nothing fancy.

    Plugin Author Internal Links

    (@internallinkjuicer)

    I am sorry, but without taking a deeper look into your system we are not able to reproduce the wrong behavior on our end.

    Unfortunately (and for good reasons), it is not allowed by WordPress to ask for credentials or anything related to that. So I have to close this topic at this point and mark it as solved. I hope for your understanding.

    Thread Starter adsim

    (@adsim)

    I could send you credentials for a test environment where the wrong behavior also happens.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I could send you credentials for a test environment where the wrong behavior also happens.

    @adsim If you do and if @internallinkjuicer accepts (and that will come out) then I will disable the plugin author’s access to these forums and recommend to the plugins team removes their plugin from the WordPress repo permanently. This is that serious. Even for a “test” environment.

    Had the developer asked for admin then this would have been the reply from me.

    NOTE: The developer did not ask for that access here. I am just explaining.

    While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

    If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

    Thankfully are other ways to get information you need:

    You get the idea.

    We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

    When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

    Thread Starter adsim

    (@adsim)

    Ok. I understand.

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