Forum Replies Created

Viewing 15 replies - 1 through 15 (of 154 total)
  • Plugin Author Antonio Villegas

    (@avillegasn)

    Thanks for your review!

    Plugin Author Antonio Villegas

    (@avillegasn)

    Thanks for the kind words, @drokita

    Plugin Author Antonio Villegas

    (@avillegasn)

    Closed due to inactivity.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Thank you for your message — the error code helps a lot.

    The message:

    “You do not have permission to post to any of the profile_id’s provided.” (code 1011)

    is not coming from Nelio Content directly. It is coming from Buffer, which means the issue is related to the connection between Buffer and your X (Twitter) account.

    This usually happens for one of the following reasons:

    1. The X account is no longer properly connected inside Buffer.
    2. The authorization token for the X account has expired or been revoked.
    3. The X account was removed and re-added, but the internal profile ID changed.
    4. The Buffer plan no longer includes that social profile.

    What to do next

    Please try the following steps inside Buffer:

    1. Go to Buffer → Channels
    2. Check whether your X account appears as connected.
    3. If it does, disconnect it.
    4. Reconnect the X account and grant all requested permissions.
    5. Then re-connect the profile in Nelio Content.
    6. Finally, try sending a new test message from Nelio Content.

    If the issue persists after reconnecting, the problem is almost certainly on the Buffer side, and you may need to contact Buffer support to verify that:

    • Your X account is properly authorized
    • Your plan supports posting to that profile
    • The profile ID hasn’t changed

    Since the error is generated by Buffer’s API, fixing the authorization there should resolve the problem.

    Let us know how it goes, and we’ll gladly continue helping if needed.

    Plugin Author Antonio Villegas

    (@avillegasn)

    We just released version 4.2.1 with fixes the reported vulnerability.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Thanks for bringing this up.

    We’re aware of the report and are actively working on a fix. While the issue does require authenticated access with Contributor-level permissions or higher (so it cannot be exploited by anonymous visitors), we agree that it should be addressed promptly.

    The fix is already in progress and we expect to release an update shortly. As soon as it’s available, we’ll publish it via the usual plugin update process.

    In the meantime, we recommend the usual best practices: keep WordPress and all plugins up to date, and only grant Contributor (or higher) access to trusted users.

    Thanks for your patience, and we appreciate you flagging this.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Got it — there are two separate things getting mixed together here, and that’s what’s causing the confusion 🙂

    This part is the key issue:

    URL contains "page?source=newsletter" → Page not found

    That happens because page is not your homepage URL.
    When you visit:

    https://example.com/page?source=newsletter

    WordPress is trying to load a page with the slug page, which doesn’t exist — so you get a 404. The popup logic never even gets a chance to run.

    How to do this correctly (step by step):

    1. Your QR code should point to the homepage, just with a query parameter added. For example: https://example.com/?source=newsletter
    2. For the popup location, select “Show on Selected Groups”. Then, select “Content is” and “Home Page”.
    3. For the popup triggers, select “Page view”.
    4. And finally, for the popup conditions, select “Query Parameter”. In the query parameter name type source. Then select “has value equal to” and in the “Value” field type newsletter.

    This means:

    • Visitors who land on the homepage with that URL parameter and value → popup shows
    • Visitors who land on the homepage normally → no popup
    • Visitors on other pages → no popup
    Plugin Author Antonio Villegas

    (@avillegasn)

    Short answer: yes, you can trigger a popup from a QR code, but not by using the “referrer” condition—and a QR code itself isn’t the issue.

    A QR code is just a way to open a URL. When someone scans it, the visit usually comes from:

    • the camera app,
    • a QR scanner app, or
    • the operating system itself.

    Because of that, there is often no reliable referrer URL, or it’s something generic (e.g. the scanner app), so a “referrer = specific URL” condition won’t trigger the popup. That’s expected behavior.

    The correct way to do this is as follows. The usual and recommended approach is to control the popup using the destination URL itself, for example:

    1. URL parameter
      • Use a QR code that points to something like:
        https://example.com/page/?show-form=1
      • Then set the popup to trigger when that URL parameter is present.
    2. Dedicated URL: Create a specific landing page just for the QR code and set the popup to always show on that page.

    All of these work regardless of whether the visitor arrived via QR code, email, ad, or manual typing.

    This isn’t a QR-specific feature, and no special QR integration is required. Note that you will need the premium version to set up the popup to open when the URL contains a specific URL parameter (case 1 above). The free version will let you set up the popup to open on a specific page (case 2).

    Plugin Author Antonio Villegas

    (@avillegasn)

    Hi @jeffhilles

    At the moment, Truth Social does not offer an official API for third-party apps to publish content. Since Nelio Content only integrates with networks that provide official APIs, we’re unable to add Truth Social right now.

    If Truth Social ever releases an official publishing API, we’ll be happy to evaluate it and adding support in a future update.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Hi @mr_milo

    We’ve just released Nelio Popups v1.3.0, which allows negative offsets in the shadow.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Hi @mr_milo

    We’ve just released Nelio Popups v1.3.0, which improves how the popup looks in the editor.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Hi @afijadior

    You are absolutely right—this CSS rule is unnecessary, and we’ll remove it from our code. The fix will be included in the next release of Nelio Content (version 4.0.7), ensuring it no longer affects the discussion popup.

    Thank you for bringing this to our attention and for taking the time to report it. We really appreciate your help in improving the plugin.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Hi @mr_milo. I understand the frustration, thanks again for your feedback. We’ll try to explore how to show the popup content with the proper width in the block editor. I’ve added this in our development roadmap. Again, thanks for sharing your feedback with us. That makes us improve Nelio Popups.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Hi @mr_milo. Thanks for your feedback. I’ve added your request of setting negative values in the shadow offsets in our development roadmap for a next release of Nelio Popups.

    Plugin Author Antonio Villegas

    (@avillegasn)

    Thanks for the kind words @nmrockswp. We will take your suggestions into account for the next version of Nelio Popups.

Viewing 15 replies - 1 through 15 (of 154 total)