JV-PostMaster - Configuring Component

You may read this article to configure the configuration settings for JV-PostMaster

General Tab SettingsBasic:

Email Address: Provide an email address to receive any communication that will be sent by JV-PM to you
Select URL Shortening Service to Use: You can decide to use between tinyurl.com and bit.ly. These are 2 different and popular URL shortening services. URLs are usually shortened when they are added to Twitter and Facebook post updates.
Provide your bit.ly login username and API Key: Provide your bit.ly API Key If you have chosen bit.ly as the URL shortening service, then you need to create a free account at http://bit.ly and then visit your account settings in bit.ly and get your login username and API key. Provide those values in these fields
Default Poster: In cases when the posting has to be done and actor (user who is performing it) is not known, this user will be assumed to be the default value. 
Secret Key for Cron Jobs: Provide a simple 5-6 long alpha numeric combination (without spaces and special characters) string. For e.g. abcad12 or 345sfjf etc.. Click on save before proceeding. This secret key will be used to verify that you are indeed running the cron job, and will prevent unauthorized execution of the job anytime. DO NOT SHARE THIS KEY WITH ANYONE.

Publishing:

Delayed Posting Duration (in min): Usually when you save an article, JV-PM queues and publishes it almost immediately. This sometimes creates problems if author of the article realizes that he has to correct something in the article or make some changes before posting. This option enables you to set a value in minutes for delaying the posting. Set it to 0 if you do not wish to enable delayed posting

Time gap between 2 posts for the same resource? (in hours): This is the minimum time that is required for posting a tweet for the same resource. For example, if you provide a value of 1, then tweets will not be posted again for the same resource (article) for up to 1 hour. This option prevents duplicate updates when you save an resource multiple times. A value of 0 in this field, will mean infinite time or you cannot update more than once for a resource

Cron Publisher: # Message processing per run: Number of messages that the cron publisher will pick up for posting from the message queue

Plugin Publisher: # Message processing per run: Number of messages that the publisher plugin will pick up for posting from the message queue

Maximum number of retries for posting: This is the maximum number of times, the message will be tried for posting, before being discarded from the queue

Time delay between retries: This is the time gap in minutes, between 2 successive retries during publishing

Post Error Notification:

JV-PM posts messages to provider accounts in 2 steps:

Step #1: When articles are saved in Joomla, the ingestion plugins queue the message to a global queue.
Step #2: Later when the publisher plugin runs, it picks messages from the global queue and posts them to provider accounts.

Thus the entire process is asynchronous and hence errors encountered during posting cannot be displayed on the screen after the article save. There are two ways to view these errors:
Method #1: Go to Jobs Status and view detailed status of the job (or)
Method #2: Use the Notification task that runs once every n minutes and sends you an email with the list of all errors encountered in the last n minutes. 

Run Frequency: This is the minimum time gap in minutes between two successive runs of the notification task. Set this to 0, to disable this task from running

Email Contents: You may select the content to be sent via emails for post errors. The content can include the entire job info or just the job id and error


Joomla Tab Settings

Ingestion - Post On Article Save:

Tweet when an article is saved in frontend? Set this to Yes, if you want to post to providers (facebook, jomsocial, twitter etc...) when an article/item is saved in Joomla frontend

Tweet when an article is saved in backend?: Set this to Yes, if you want to post to providers (facebook, jomsocial, twitter etc...) when an article/item is saved in Joomla backend

Post update, only when an article is saved first time?: If yes, then posting will be done, only when the article is saved and published the first time. Subsequent saves (which are edits to the article) will not post any update. You may make multiple edits in unpublished state and then finally set it to Published to post to provider accounts, as well. 

How do you want JV-PM to handle articles being saved, with publishing date set to the future?: You may either decide to not queue the item for posting or queue the item and post it when the article is published!

Twitter Specific:

Prefix word or phrase to pre-pend article tweets: This option is applicable only for posting to Twitter. The prefix phrase will be prepended to the tweet message while posting.

Hash Tag for tweets: This is the hash tag that is used in twitter for searches.

Tumblr Specific:

Hash Tag for posts: This is the hash tag that is used in twitter for searches.

General:

By default articles of all authors will be tweeted. You may provide exceptions here (Give usernames, one per line):Provide joomla usernames of those members, whose articles (author) should be not posted to providers.

Generate SEF URLs for posted URLs?: This feature is for experimental purposes only, as Joomla does not support SEF URL generation from Joomla! backend. If you do not get proper SEF URLs with this option, then you may turn this option off

Author Exceptions: By default articles of all authors will be posted. You may provide exceptions here (Give usernames, one per line)

Cron Configuration:

The default way to ingest and publish info to social media is when you save articles. There is an alternate way to do this, which works even better when you want to pick content from automatic article generation components like Article Generator, FeedGator etc... JV-PM can monitor Joomla database tables for resources, identify the newly created/generated articles from it, and will start the ingestion and publishing process. This needs a cron job to be added via your hosting control panel. This section provides the cron job command that need to be used. 


K2 Tab Settings

Ingestion - Post On Item Save:

Tweet when an item is saved in frontend?: Set this to Yes, if you want to post to providers (facebook, jomsocial, twitter etc...) when an article/item is saved in Joomla frontend

Tweet when an item is saved in backend?: Set this to Yes, if you want to post to providers (facebook, jomsocial, twitter etc...) when an article/item is saved in Joomla backend

Post update, only when an item is saved first time?: If yes, then posting will be done, only when the item the first time. Subsequent saves (which are edits to the article) will not post any update 

How do you want JV-PM to handle items being saved, with publishing date set to the future?: You may either decide to not queue the item for posting or queue the item and post it when the article is published!

Twitter Specific:

Prefix word or phrase to pre-pend item tweets: This option is applicable only for posting to Twitter. The prefix phrase will be prepended to the tweet message while posting. 

Hash Tag for tweets: This is the hash tag that is used in twitter for searches.

Tumblr Specific:

Hash Tag for posts: This is the hash tag that is used in twitter for searches.

General:

Image Source: This option is for posting to facebook and jomsocial accounts only. When you select {article-description} as a part of the tweet message, an image from the item is also posted. In this option you can decide which image to post.

By default articles of all authors will be tweeted. You may provide exceptions here (Give usernames, one per line): Provide joomla usernames of those members (author), whose items should be not posted to providers.

Generate SEF URLs for posted URLs?: This feature is for experimental purposes only, as Joomla does not support SEF URL generation from Joomla! backend. If you do not get proper SEF URLs with this option, then you may turn this option off

Cron Configuration:

The default way to ingest and publish info to social media is when you save articles. There is an alternate way to do this, which works even better when you want to pick content from automatic article generation components like Article Generator, FeedGator etc... JV-PM can monitor Joomla database tables for resources, identify the newly created/generated articles from it, and will start the ingestion and publishing process. This needs a cron job to be added via your hosting control panel. This section provides the cron job command that need to be used. 

EasyBlog Tab Settings

Post on Blog Post Save:

Tweet when an item is saved in frontend?: Set this to Yes, if you want to post to providers (facebook, jomsocial, twitter etc...) when an article/item is saved in Joomla frontend

Tweet when an item is saved in backend?: Set this to Yes, if you want to post to providers (facebook, jomsocial, twitter etc...) when an article/item is saved in Joomla backend

Post update, only when an item is saved first time?: If yes, then posting will be done, only when the item the first time. Subsequent saves (which are edits to the article) will not post any update 

How do you want JV-PM to handle items being saved, with publishing date set to the future?: You may either decide to not queue the item for posting or queue the item and post it when the article is published!

Twitter Specific:

Prefix word or phrase to pre-pend item tweets: This option is applicable only for posting to Twitter. The prefix phrase will be prepended to the tweet message while posting. 

Hash Tag for tweets: This is the hash tag that is used in twitter for searches.

Tumblr Specific:

Hash Tag for posts: This is the hash tag that is used in twitter for searches.

General:

Image Source: Decide which image to post.

By default articles of all authors will be tweeted. You may provide exceptions here (Give usernames, one per line): Provide joomla usernames of those members (author), whose items should be not posted to providers.

Generate SEF URLs for posted URLs?: This feature is for experimental purposes only, as Joomla does not support SEF URL generation from Joomla! backend. If you do not get proper SEF URLs with this option, then you may turn this option off

Cron Configuration:

The default way to ingest and publish info to social media is when you save articles. There is an alternate way to do this, which works even better when you want to pick content from automatic article generation components like Article Generator, FeedGator etc... JV-PM can monitor Joomla database tables for resources, identify the newly created/generated articles from it, and will start the ingestion and publishing process. This needs a cron job to be added via your hosting control panel. This section provides the cron job command that need to be used. 

Still need help? Contact Support Contact Support