New version breakes Kadance Theme Progress bar

Home Forums Product Support Forums Ajax Search Pro for WordPress Support New version breakes Kadance Theme Progress bar

This topic contains 9 replies, has 2 voices, and was last updated by Ernest Marcinko Ernest Marcinko 3 months, 4 weeks ago.

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #47029
    niklas
    niklas
    Participant

    Hi, for some reason, the latest version breaks our Kadance Theme progress bars.

    Is there a way to roll back a version? And if there is there any known fix for this being worked at, has someone else reported this>?

    #47030
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi,

    Can you please add more details about the issue?

    We have no reports of similar issues yet.I would like to test and debug this, can you please add temporary FTP and back-end details? I also need to know how to exactly replicate this issue:
    – Which page or pages to visit
    – What actions to take exactly
    – What should or should not appear
    – Any other useful details

    Rolling back is a terrible idea, it’s better to fix any existing issues.

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #47033
    niklas
    niklas
    Participant
    You cannot access this content.
    #47051
    Ernest Marcinko
    Ernest Marcinko
    Keymaster
    You cannot access this content. Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #47053
    niklas
    niklas
    Participant

    I do apologize, I must have not clicked add a user at the end whilst putting all the information together.

    The user is now added with the same details as previously provided.

    #47065
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Thanks!

    I had investigated the issue from top to bottom, and it seems that for some reason an post metadata is triggered to update and the search tries to re-index that post during the trigger, because this option was activated.

    It should be fine, but in this case rendering the block during that event very likely fires a hook, which should be used later, and then it’s not rendered correctly anymore. Anyways, I have deactivated that option, now it’s all right.
    I tried to look for a possible way around to have that feature active as well as bypassing the issue, but it’s not possible as I don’t know what hook fires exactly, and it’s better not to fiddle with it, it may cause even more problems.

    Luckily this is not a bug for fixing, so this should resolve it permanently.

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #47085
    niklas
    niklas
    Participant

    Thank you so much for figuring this out 🙂

    Will get a couple of more licenses to use on my other 2 sites shortly.

    #47086
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    You are very welcome 🙂

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #47087
    niklas
    niklas
    Participant

    Forgot to say.

    Just as some bonus info, that might be good to know, we never changed any settings after updating so it might be that this gets enabled OR that it was working before.

    regardless, it is not a needed feature for us 🙂

    #47088
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Oh, I will make sure to look into it, that should be turned off by default for sure. Thank you for the feedback!

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.