• Resolved psn

    (@psn)


    Since your last versions the custom terms and tax has dissapeared from scroll box so now my table press updates is not available. Can you quickly investigate and fix so we get back the custom terms asap?

    I have also noticed that no mail is sent for post_updates.

    Per

    https://wordpress.org/plugins/bnfw/

Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Author bnfw

    (@voltronik)

    Hi Per,

    I will investigate as soon as I can today.

    Are you still getting notifications or is it only that they’ve disappeared from the drop-down box?

    Thanks,
    Jack

    Thread Starter psn

    (@psn)

    No I dont get any notifications and all custom post types is gone from your latest versions. I have now tested to download ver 1.1 and then I get back all custom post types but still no notifications sent for post_updates.

    Per

    Plugin Author bnfw

    (@voltronik)

    Hi Per,

    I have tested 1.1.5.2 and see that the TablePress custom post type does’t show in the list but regular custom post types show fine.

    I will continue to investigate. Hang tight.
    Jack

    Plugin Author bnfw

    (@voltronik)

    Just tested ‘New Post Published’ and ‘Post Updated’ for both regular posts and custom post types and all are working for me.

    Is it a specific post type that’s causing you issues?

    Thread Starter psn

    (@psn)

    Its strange, its working for some of my mailadresses but I dont get any to my @gmail.com account or @home.se accoount. I have an email log inside WP and there I can see all seems to be sent but not arrived so they seems to be stucked somewhere in cyberspace 🙂

    Plugin Author bnfw

    (@voltronik)

    Ah, ok, in that case it’s worth checking your spam folder or spam filter.
    It’s also worth enabling DKIM and SPF for both your server hosting your website and email accounts if possible too. This should reduce the risk of emails getting marked as spam.

    I’m hoping that with an upcoming version you will be allowed to change the default email address that emails are sent from and this should cut down on email hosts marking anything from ‘wordpress@’ as spam.

    Hope that helps!
    Jack

    Thread Starter psn

    (@psn)

    Sorry but whats DKIM and SPF?

    No mail is comming at all so no mail in spam either.

    Per

    Plugin Author bnfw

    (@voltronik)

    DKIM: http://en.wikipedia.org/wiki/DomainKeys_Identified_Mail
    SPF: http://en.wikipedia.org/wiki/Sender_Policy_Framework

    If the log in WordPress says that the emails are getting sent out then the problem lies elsewhere. I won’t be able to help with this as it’s outside the scope of the plugin but hopefully it’ll help you look in the right direction.

    Thanks,
    Jack

    Thread Starter psn

    (@psn)

    I think I know whats the issue is, I’m right now at work behind several proxy servers and that might be reason for failure. I will test more when I come home and see if this issue persist.

    I know its has been working yesterday so I think we can drop this sending issue for time being and concentrate on the Custom post type to get this back in next version of BNFW.

    Per

    Plugin Author bnfw

    (@voltronik)

    Hi Per,
    Sounds likely to me.

    With regards to TablePress, i’ve hit a wall and i’m afraid there’s no way around it.
    TablePress has set their custom post type to be private to prevent other plugins from interfacing with it. This was causing tonnes of issues with BNFW and was preventing notifications from being sent out for new posts, posts updating, etc so I had to change this to only show public post types in the drop down list when adding a new notification.

    I’ve investigated lots of avenues but there’s no way for me to fix this unless TablePress change the way they register their custom post type. I’ll be adding this to the documentation for BNFW shortly.

    If you’d like to see a change, i’d recommend getting in touch with the author of TablePress to see if they’d consider changing their post type from private to public. Short of this, there’s really nothing more I can do about how other plugins integrate with WordPress.

    Although probably not what you want to hear, at least it should provide an honest and transparent explanation of the problem.

    Thanks,
    Jack

    Thread Starter psn

    (@psn)

    Ok, I will contact them at omce and will get back as soon as they have answered.

    Per

    Thread Starter psn

    (@psn)

    Heres Tablepress’s authors answers:

    “TablePress only uses CPTs as the data storage, where the table is stored as a JSON-encoded string. Making those public is not useful for TablePress, and could actually confuse people (as they would suddenly see the JSON code).
    Can you explain why you want the TablePress CPT to be public? (If you really want this, you could achieve it by using the tablepress_post_type_args filter hook from the model-post.php file.)”

    Per

    Plugin Author bnfw

    (@voltronik)

    Hi Per,

    That makes sense. You’ll need to drop some code interacting with the tablepress_post_type_args hook as the author suggests into your functions.php file if you want to expose the post type to be public.

    Hope that helps.
    Jack

    Thread Starter psn

    (@psn)

    Ok, any tip for how this code should look like to get this working?

    Per

    Plugin Author bnfw

    (@voltronik)

    Not from my end, no – but the TablePress author might be able to help!

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘No custom term or tax’ is closed to new replies.