Hi,
These are PHP Notices so the plugin is going to work even with these.
Maybe you should first try creating new test post and seing if it’ll be auto published to your twitter and facebook account.
After that if you want to make work the Auto Publish Old Posts we have a FAQs you can take a look. http://efficientscripts.com/support/microblogposter/faqoldposts
Thanks
Thread Starter
BeoR4
(@rr44)
Hi there,
Nope, sadly, publishing a new post does not result in any plugin log or WP log entries or posts on the permanently authorised SNs (Twitter and FB)…
Is there anything else should I check?
Re old posts : I should have said that our cron is triggered via a permanent 5min unix cron cycle run by our hosting co Pressidium, but I did also do the manual wpcron job runs that failed that I mentioned. Wpcron is working otherwise.
Thanks again,
R.
Thread Starter
BeoR4
(@rr44)
BTW I waited for a period of time after publishing the new post. I am guessing that new post auto posting is filter trigger based and not wpcron based…
Hi,
When you write a new post please have a look bellow content of your post at field “Disable Microblog Poster this time?” and make sure you didn’t disable it.
Auto publishing is triggered when you make a new post with ‘publish_post’ event
New post auto posting is not wpcron based
Kind regards!
Thread Starter
BeoR4
(@rr44)
Hi there,
Ahem, yes indeed, the new post posting did not work because that was ticked… I had no idea it was there. Thank you! Strangely the old post posting starting working when I reactivated it after that preceding new post autopost 🙂
The issue I now face is how to get WP shortcodes to be work properly. I don’t mean the plugin ‘internal’ shortcodes – so I don’t mean {TITLE} , {MANUAL_EXCERPT} , {EXCERPT} , {CONTENT_FIRST_WORDS}.
For example, the successful post content included visual composer shortcodes. That happened for Twiter and FB contetent via {CONTENT_FIRST_WORDS} and for FB when {EXCERPT}. What is the best way to deal with that? Pretty much all our content has such shortcodes….
Many thanks,
R
Thread Starter
BeoR4
(@rr44)
As an example it’s stuff like [vc_row][vc_column][vc_column_text][vc_row bg_type=”image” parallax_style=”vcpb-default” that comes out as the post content from the plugin.
I guess I have missed something (I did ask google…)
Thanks again,
R
Hi,
You should enable in Microblog Poster in General options the last field which is ‘Apply filters prior to auto publishing’.
When you enable it your WP shortcodes should be rendered correctly.
Kind regards!
Thread Starter
BeoR4
(@rr44)
Hi there,
Thanks again. I did/do have “Apply filters prior to auto publishing” ticked though 🙁
On a related topic, the wording on that options page did make it look as if only the following shortcodes are filtered:
Shortcodes filtered : {TITLE} , {MANUAL_EXCERPT} , {EXCERPT} , {CONTENT_FIRST_WORDS}
Does that only those internal plugin shortchodes in {} braces are used to construct social autoposts, or that WP shortcodes can be used in your internal {} shortcodes?
Thanks again!
You’re right yes. The only shortcodes that are filtered are those ones:
Shortcodes filtered : {TITLE} , {MANUAL_EXCERPT} , {EXCERPT} , {CONTENT_FIRST_WORDS}
How do you use the wp shortcodes [vc_row][vc_column][vc_column_text]? In the post description or elsewhere?
Thread Starter
BeoR4
(@rr44)
Hi there,
[vc_row][vc_column][vc_column_text] etc are in the actual post ‘body’ content to provide formatting etc. and other things for Visual Composer (a quick but heavy editor for the time deprived!).
There are times that have other shortcodes are in the content too/instead, which generate actual readable content from dynamic meta fields – like maybe a price. Or even to include static text that is shared in common across posts, etc.
Does that make sense?
Hi,
If you don’t have the desired result when ‘Apply filters prior to auto publishing’ is checked then it means that what we implemented in the case it is checked don’t cover your wp shortcodes.
Please tell us the plugin you’re using and we could investigate. We don’t guarantee we will make it work but rather provide a clear answer.
Thread Starter
BeoR4
(@rr44)
Hi there,
Sorry for the delay – was in a car crash….
The extension is Visual Composer @ https://vc.wpbakery.com/
It really is the most widely used of its type, so I think it would be good for your plugin to ignore/exclude/account for their shortcodes.
Or perhaps maybe better just exclude anything inside square [ ] brackets as a general policy or as an option? If that is simpler? Might make sense, unless I am oversimplifying….
V best,
R
-
This reply was modified 9 years, 2 months ago by
BeoR4.
