Extraneous output

  • Resolved Pioneer Web Design

    (@swansonphotos)


    9 years, 2 months ago

    On one of my sites, I began seeing this text output on a specific Custom Post Type and standard posts. The site is using a Child Theme of Twentyeleven and the Events Calendar plugin (which oddly this extraneous HTML is not output on the events custom post types).

    Displayed:

    triggers: a:0:{}
groups: a:0:{}
alerts: a:0:{}

    The HTML on these posts is:

    <ul class="post-meta">
<li><span class="post-meta-key">triggers:</span> a:0:{}</li>
<li><span class="post-meta-key">groups:</span> a:0:{}</li>
<li><span class="post-meta-key">alerts:</span> a:0:{}</li>
</ul>

    I can see in the file /wp-content/plugins/stream/extensions/notifications/ui/js/form.js that it is the Stream plugin adding the Custom Fields. What I do not understand is why this text is outputting as noted nor can I see how to correct this other than deactivating the plugin, which I have, but would like to use on this site.

    Any thoughts?

    https://wordpress.org/plugins/stream/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Frankie Jarrett

    (@fjarrett)

    9 years, 2 months ago

    Hello there, I’d be happy to help get this issue resolved.

    1. What version of WordPress and what version of Stream are you using?

    2. Can you list all the plugins that you have activated? This will help us replicate an environment similar to yours.

    3. Can you confirm if this text output is seen in the admin area only or also on the front-end?

    4. Could you upload a screenshot here for us to see?

    Thread Starter Pioneer Web Design

    (@swansonphotos)

    9 years, 2 months ago

    1. Both are the latest.

    2. Other than your plugin:
    Comprehensive Google Map Plugin
    Gravity Forms
    Gravity Forms PayPal Standard Add-On
    The Events Calendar
    WordPress SEO
    WP-PageNavi
    WP Responsive Menu
    Jetpack by WordPress.com
    —The following modules are active for Jetpack:
    -JSON API
    -Photon
    -Subscriptions
    -Widget Visibility

    3. It is output in the content of the post. I published a post in a cat. not easily found on the site here.

    4. Is above enough?

    Frankie Jarrett

    (@fjarrett)

    9 years, 2 months ago

    I think I have found the root cause and have created a bug report for it here: https://github.com/wp-stream/stream/issues/693

    Thank you for reporting this!

    Thread Starter Pioneer Web Design

    (@swansonphotos)

    9 years, 2 months ago

    I will continue to follow up there and/or look for a fix from Stream directly soon.

    Thank you!

    Frankie Jarrett

    (@fjarrett)

    9 years, 2 months ago

    In the meantime, you can put this code in your theme’s functions.php file to remove the unwanted meta from your other post types.

    https://gist.github.com/fjarrett/be5423e0899895558d75

    Don’t leave this in your functions file, because it will run on every page load. You should remove it after you’ve refreshed at least once. Also, it might take a while to refresh the first time depending on the number of posts you have.

    This code fixes the problem from happening on future saves: https://github.com/wp-stream/stream/pull/694/files

    It will go out in the next release.

    Thread Starter Pioneer Web Design

    (@swansonphotos)

    9 years, 2 months ago

    @frankie,

    Thank you for taking the time to work on this. I do have a few questions and notes.

    1. The code at github just removes the post meta key pairs from the db based on post id and posts with the ‘trigger’ meta value (which can also be done manually). Very well. Just a side note on this. First, only ‘new’ posts added to site after activating Stream have the post meta, but this includes posts that are in trash, auto-saves, and notably posts that have been deleted from trash. The meta is not removed when the post is fully deleted. Should it not be?

    2. Is the revision noted at pull/94/files fully tested?

    3. Do you have a time frame for next release? I can live without this plugin for now much more that I would want to add any additional issues to this live site.

    If I have time soon, I can test on a dev site.

    Again, thank you very much.

    Frankie Jarrett

    (@fjarrett)

    9 years, 2 months ago

    1a. Right, new posts will continue to have the unwanted meta until the new version of Stream is in use.

    1b. Post meta is removed when a post is deleted permanently, that is how WordPress core works. So if you are looking directly at the database table, no post meta entries should exist for post IDs that have been deleted.

    2. Well, I’ve tested it and it’s working for me 🙂 Would be great if you could confirm as well.

    3. Yes, we’ll probably do another release tomorrow or Monday. I shy away from issuing releases on Fridays.

    Frankie Jarrett

    (@fjarrett)

    9 years, 2 months ago

    Also, I’ve merged the PR so when you get around to testing this you can just use the latest package on the develop branch.

    https://github.com/wp-stream/stream/archive/develop.zip

    Thread Starter Pioneer Web Design

    (@swansonphotos)

    9 years, 2 months ago

    1a. I can verify.
    1b. I can verify that the post-meta is not being deleted for posts in all cases. I was in fact viewing the db directly and viewed then each post id that had the triggers, alerts or groups key set. (Edit: text removed.) I can confirm the posts had been trashed, then permanently deleted, but the post meta remained.
    2. I will likely have time over next few days to test.
    3. Good!

    Frankie Jarrett

    (@fjarrett)

    9 years, 2 months ago

    Just released 2.0.3 which fixes the issue in this thread.

    https://wordpress.org/plugins/stream/changelog/

    Thread Starter Pioneer Web Design

    (@swansonphotos)

    9 years, 2 months ago

    I have updated to 2.0.3 and note that the issue is resolved.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Extraneous output’ is closed to new replies.