DraftPress Team

Forum Replies Created

Viewing 15 replies - 166 through 180 (of 180 total)
  • Plugin Author DraftPress Team

    (@draftpress)

    @dimalifragis thank you for notifying us of this. Our dev team is looking into it and will release an update soon to handle the warning you’re seeing.

    thank you

    Plugin Author DraftPress Team

    (@draftpress)

    Great to hear! If you got a few seconds, please leave us a review so we can keep this plugin free and support it like we did here.

    And if you ever consider the PRO version, it’s currently on a lifetime deal over at RocketHub.

    I’ll close the ticket.

    Thank you.

    Plugin Author DraftPress Team

    (@draftpress)

    Hi @rimoreno – We see the snippets are inside the head tag.

    Plugin Author DraftPress Team

    (@draftpress)

    What’s the site URL / Page URL?

    Plugin Author DraftPress Team

    (@draftpress)

    @rimoreno – It sounds like he’s likely looking at a cached page. Go ahead and clear cache from your site / server. Try thereafter. He can also just try in a browser he hasn’t visited before.

    Thank you.

    Plugin Author DraftPress Team

    (@draftpress)

    Thank you very much for taking the time to review our plugin.

    Plugin Author DraftPress Team

    (@draftpress)

    Hi @oddcomments – We have that feature available on the Pro version of HFCM.

    Thank you very much.

    Plugin Author DraftPress Team

    (@draftpress)

    Hi @michaelfischerat

    We had a look into the issue. Tested the plugin with the Avada theme, with the same location you are having issues with. Everything worked just fine.
    We also checked the page which has the duplicate snippet. The page has an unusual HTML structure i.e it has multiple <body> tags, multiple <HTML> tags which could be an issue. We suspect that maybe something is triggering the hook twice on the page due to maybe bad HTML or some function inside of the theme. Can you please try resolving the structure issue, also check if the hooks are triggering multiple times, and see if that helps solve the duplicate snippet issue?

    Thank you

    Plugin Author DraftPress Team

    (@draftpress)

    Since we have:

    1) Tested it with a clean copy of Avada
    2) have no other reported cases of this issue out of almost 350,000 active sites using this plugin of which I’m sure there are many using Avada as it’s popular

    We can only assume this is related to either a conflict with third party plugins or customized code (theme or other).

    Without being able to see it, there’s no other possible way to help us troubleshoot even though we’re willing to do so.

    Thank you.

    Plugin Author DraftPress Team

    (@draftpress)

    @takioh the editor we have is an HTML code editor hence the suggestions don’t apply to PHP code, you can simply ignore editor suggestions for now. This is one of the enhancements we have on our roadmap for our PRO version. You can check it here: https://app.loopedin.io/header-footer-code-manager-pro

    Plugin Author DraftPress Team

    (@draftpress)

    @afterhoursolutions – Do all the other categories actually have at least 1 post assigned to them? If not, then they would not show up.

    Let us know if this is not the case.

    Plugin Author DraftPress Team

    (@draftpress)

    IF you purchase the LTD from RocketHub – clearly noted there:
    https://www.rockethub.com/deal/header-footer-code-manager-pro-wordpress-plugin
    “30-day money-back guarantee, no matter the reason”

    IF you purchase directly from DraftPress – clearly noted almost on every page:
    “If the product does not work as advertised and we cannot fix it within 30 days of notification, we will refund your purchase. No questions. No risk. Period.”

    Yes. To improve the product, we do encourage people to share why. Believe it or not, more than 50% of the time, it’s simply because they didn’t know how to do something. This is quite a reasonable ask in the plugin industry and I can point to several other well known brands that say the same.

    About revoking my rights – I had to confirm that I will not want refund during the first 14 days period.

    Can you point us to where you saw this ^ statement. It’s possible we missed updating it and will do so as it’s inconsistent with our 30-day refund offer.

    Plugin Author DraftPress Team

    (@draftpress)

    Hi @pumpaxxl – I will do my best to respond to each point and any of the PRO related ones can be taken to the premium support team. The FREE ones we can resolve here if actual bugs.

    There are several comments in this thread and some of them require more context. We’re all for someone providing a honest review but do feel this one is unwarranted if it’s not specific to the FREE version and actual facts.

    1] Firstly, to ensure we stay compliant and use this forum for the free plugin, just a clarification below:

    We have various team members. Some monitor our free plugins. Some our PRO. Please direct accordingly and for quick reference, here are the channels to use for the PRO support team:

    PRO SUPPORT:
    a) Email is support [at] draftpress . com
    OR
    b) or you can contact the team using this form – https://draftpress.com/contact/ – which goes to the same email above.

    All FREE plugin related topics should be on these .org forums.

    This will allow the right members can assist and ensure we’re not mixing things up on this forum.

    2]

    Also, your “money back guarantee” says volumes.

    Why would you be criticizing any company that is giving YOU a no-risk guarantee (i.e. refund)? That’s a GOOD thing and definitely not a flaw and I’d be worried about any company that doesn’t stand behind their product. So this is such a weird comment unless we’re not understanding it which could be the case as it lacks needed context.

    3]

    … and I don’t appreciate forcing me to agree to revoke my legal rights before I can buy the plugin.

    Unfortunately, you’re making a bold accusation which is serious but providing zero context. We have no clue what you’re talking about. What “legal rights” are we taking away from you?

    If you don’t want to buy, don’t buy. We’ve had thousands of buyers and not a single one has ever made such a comment so please add more context if you’re making such a strong accusation so we can address it. If you don’t give a company any context, how do you expect them to even reply to such an accusation. At this point, there’s a lot of criticism without any context and it feels like you’re just trying to create harm unnecessarily. That’s not helpful.

    If this comment was related to the PRO version, please use the appropriate channel.
    If FREE, then this forum is fine.

    4]

    On the other hand the selections are the most important part and they are just basic. You will quickly hit the wall as soon as you want to do more than basic stuff. And there is a long way to go before it is convenient to use.

    Almost 400,000 active sites using it and 200+ people left 5-star reviews. You left a 2-star review. In that time, we have answered almost a thousand support tickets and have never seen or heard a single person refer to the plugin as “basic”. So can you elaborate what is “basic” mean to you? What is considered not “basic”? And let’s ensure the expectations are within the scope of this type of plugin.

    If this comment was related to the PRO version, please use the appropriate channel.
    If FREE, then this forum is fine.

    5]

    No way to move code records up and down

    This is by design. It is intentional because snippets have no relationship – they stand alone and are not a logical group. So moving them up or down has no impact or function, and instead creates confusion because it can be falsely assumed that moving a snippet up or down means one loads higher than the other. Given that a snippet has its own conditions and placements, each snippet may load on different pages making moving up/down moot and confusing.

    Having the ability to move up/down would only be valid IF and ONLY IF the group of snippets all had EXACTLY same conditions set, and in that case, the only function of dragging them up/down would be to set which snippet is “priority” over another (ordering essentially). There’s a better way to handle that which is to just create a priority field for each snippet which is exactly what was introduced in PRO recently.

    You are clearly tech savvy so I can appreciate your train of thought here but your view is only taking into account your snippets on your site. Keep in mind hundreds of thousands of other users are not as knowledgeable and don’t think in terms of web development or have the same snippets or use cases. So we have to maintain the ease of the plugin, backwards compatibility, and eliminate confusion for users who would not understand some of these nuances that you and I are intimately familiar with.

    6]

    no way to select number of record per page

    Good point. And we can certainly add this in a future release now that it’s been suggested by you. Though, here’s some historical context behind it. We previously were getting non tech-savvy users saying they couldn’t find their snippets after saving them (of course they were just on page 2 :). So we set the snippets to 20 per page instead of the default of 10. We never got the same ticket again.

    Like you suggested, we can introduce the “Screen Options” setting and allow folks to set their own number. If we can do this and still keep the default to 20, we will make this update it in a future version.

    7]

    you added the priority but se all the existing records to priority 0 instead of something in the middle. Now we have to go through each of them the set is so some can have higher priorities. We have sometimes 40 records and it is tough job to handle them with your plugin.

    This is related to PRO it seems but will respond here.

    This is also by design and an appropriate way to handle it given this feature was just introduced. Why? Because we have to care about backwards compatibility for the thousands of users and sites and configurations / use cases they all have. Therefore when we introduced this feature, we had to be conscious of the fact that prior to this NEW feature, no one had a “priority” on their respective sites. So setting it to 0 as the default value is not only correct, but is intentional to avoid breaking anyone’s sites or snippet logic. So if a user’s snippet settings were fine as-is before the new feature, they’d have to change nothing UNLESS they wanted to start setting priorities of any snippets.

    Regardless, let’s pretend we had set all of them to 5 like you’re suggesting, you’d still have to modify your priorities for your own site and preferences. And someone else would ask why we set them to 5 and not 0 or 10. So I’m not sure how that would change anything other than a lot of users confused and sending support tickets asking why all their snippets priority is set to 5. What is your suggestion of the right value and approach that would please everyone and ensure backwards compatibility and ensure you specifically didn’t have to configure your respective site’s 40 records?

    Hope these responses add more color and context to your points. If you’d like to change your review, do so. If you still think such a plugin is 2-stars, we respect that.

    Thank you.

    Plugin Author DraftPress Team

    (@draftpress)

    Thank you for the review @grafite

    Plugin Author DraftPress Team

    (@draftpress)

    Hey @samedwards, this was reviewed and all the necessary changes were implemented in the last published version. Please update to the latest version. Thank you.

Viewing 15 replies - 166 through 180 (of 180 total)