# Troubleshooting

# Requests

# Why modified articles, in the published state, are not processed?

By default, AutoTweetNG only processes new content items. Content modification can be enabled at plugin level to be received.

For example, if articles are initially created as unpublished and, in a second instance, modified to be published, then they are not processed. To enabled article modifications, in System - AutotweetContent plugin, Posting filter/Process modifications=Yes. This setting is a general method to publish all content modifications.

When Process modifications is enabled, every time you save, a new 'modified' event is fired and a new request is added in a 60-seconds window. You can increase this window to add a delay, deliver fewer requests and sum all changes in a single request (Options/Advanced/Content Polling/Minimum requests polling delay).

INFO

On the other hand, Joocial has an interactive tool Post manager to choose when an article has to be pushed (Post This=Yes) into the publishing queue (or not, Post This=No). Joocial - Post This

Ref: How content can be republished?

# There are requests in the list, waiting to be published, but they are not delivered, why?

AutoTweet and Joocial are designed to avoid any overload on your website while it processes social posts. Hence, there is always a delayed publication, caused by Social Channel API processing times. By default, in Page Load mode, only when front pages are visited, Requests and Posts are processed by the Automator plugin (every 2-3 minutes).

The processing modes are:

  • Manual,
  • Automator Plugin (default), or
  • CRON job task (available only in AutoTweetNG PRO and Joocial).

Running in Automator Plugin mode (default), posts are only processed when the front website is visited. If your site does not have visits on the front site, AutoTweet does not process waiting requests and posts.

On the other hand, you can manually click Process for Requests or Publish for Posts to publish them, or schedule a CRON job task to work in fixed intervals.

If you plan to configure the CRON job task, please, check these steps:

# AutoTweet does not detect articles imported from RSS feeds

AutoTweet detects new articles even if they are inserted from others third-party extensions.

However, since AutoTweet checks the database applying time filters, new articles have to be published within a certain date range.

If the articles are not detected, please, try to increase the polling window to include a bigger date range.

You can find the Polling window (hours) parameter in: Control Panel / Options / Advanced settings / Content Polling Settings / Polling window (hours).

After you change the parameter, it is going to retrieve the articles, within the new polling window, in the next check.

# Evergreens are published at a different fixed time, why?

If the time difference is the same, then your hosting could have time zone misconfiguration.

For instance, this misconfiguration was found in a customer site:

  • Joomla Server Time Zone = UTC
  • System Information/ PHP Information/ PHP date Default timezone = UTC
  • System Information/ PHP Information/ PHP date.timezone = America/Chicago (UTC-6, Daylight Saving Time, UTC-5)

Please, verify if each setting matches your Joomla! configuration and ask your hosting provider to update PHP Information.

# Posts

# "Immediate" posts are not published immediately, why?

In Joocial, Post This "Immediately" defines a request and a following post with the highest priority to be processed in the first place. Once a request is received, it follows the same steps of the general workflow. For example, to apply all rules and deliver the posts to all (unlimited) channels. The publishing process can be long and "Immediately" can be translated to several processing steps according to your configuration.

To deliver "Immediate" posts faster, you can increase the Cron job frequency or increase the number of processed posts in each execution (Options/ Cron job/ Max. no. of posts).

# Images with spaces in the filename are not shown on social networks, why?

It is not recommended to define URLs with spaces.

A local file can have spaces. However, a valid URL encodes space with %20 or +. Both cases are accepted in different ways in each social network, browser and device. In the end, it is better to avoid them. For instance, an article title is always translated to a slug with - instead of spaces. The same practice has to be applied to image filenames.

# I have enabled Cron job mode, posts are 'Waiting' but not delivered, why?

There are several alternative execution methods. Please, check which method works in your hosting, review hosting documentation or ask to your hosting support which method is available.

To check if Cron job command is executing, you can enable the logging mode and look for periodic executions. If they are missing, not matching your Cron job frequency definition, then it is not executing at all.

# Wrong character encoding, characters of the intro text are wrong in a published Post, why?

AutoTweeNG and Joocial are fully compatible with UTF8 and non-latin characters. Many users work with languages such as Greek, Russian, Chinese, among others.

However, PHP and MySQL UTF8 support have improved on the latest versions.

Wrong character encoding is usually associated with a legacy PHP version. Most issues are associated on the latest stable PHP versions. What is your PHP version?

Please, update to the latest PHP stable version. At this time, PHP 7.1 or superior.

# Why are social posts not published?

See There are requests on the list, waiting to be published, but they are not delivered, why?

Check if the article, category and menu are set to public access. If not, the user has to login to read the article.

Alternatively, if there is more than one menu access path, the SEF router may be choosing the restricted access. In this case, review your extension configuration or re-organize the alternative accesses to route the traffic to the right menu.

# Post is delivered with a shortened URL, but the link does not target the right item, why?

Related to: Wrong URLs in posts

AutoTweet and Joocial generate posts in the backend. Since front-end and back-end sites are different sites, a connection is opened from back-end site to the front-end site to solve the SEF query and generate the link.

If there is any issue in the SEF query, then the resulting shortened URL may be different than the real link. The most common issues in the connection are:

  • Security restrictions, preventing the connection from the back-end site to the front-end site.
  • Self-signed SSL certificate, preventing the opening of a valid HTTPS connection.
  • CloudFlare, if you implement this service, you can exclude the cronjob URL from the cache. Ref: How do I exclude a specific URL from Cloudflare's caching?

To investigate the case, please, enable the logging mode, test a case and send us the resulting logged file to check it.

# Channels

# Facebook Troubleshooting

# How can I auto-publish to my user profile in Facebook?

Facebook has deprecated user channels from the API. So, there is no longer a way to auto-publish posts to user profiles via a User Channel. To share a link, Facebook is currently enforcing the use of sharing buttons to manually share posts and links into the user profile.

# The Facebook Login button is not shown to autorize the App, why?

The Facebook Login button is shown on the page when Facebook SDK is properly initialized in the page.

If the button is not shown, these are the most common sources of the problem:

  • Another extension on the site has already initialized Facebook SDK with a different scope. Try to temporarily disable other extensions that also has Facebook Apps to confirm if there is a conflict between them. After the authorization, you can re-enable them.
  • A security extension, a CDN service or a security service is blocking Facebook Login. For instance, Cloudflare or Kaspersky Total Security are known to restrict the SDK.

# Invalid Scopes: publish_pages, manage_pages

You have created an App after 2020-05-05, then the App has API v7 or superior. Please, select the API v7 option, before authorizing the app.

# Invalid Scopes: publish_actions, publish_pages, manage_pages, user_managed_groups, user_photos

Ref: 100 - Graph error: (#100) Only owners of the URL have the ability to specify the picture, name, thumbnail or description params

After the Facebook–Cambridge Analytica data scandal, Facebook has started to implement drastic changes to the platform. There have been overnight breaking changes in a short period. Now, after the F8 event, with the release of Graph API v3 and the opening of the new App Review process, we can consider that most of the new model is ready and we can start rolling out the news to our software packages.

We have released AutoTweet and Joocial 8.20 versions to support Facebook new API. This is the first step to work with the new workflow. The current Facebook channels and Apps (v2.*) do not require changes.

These are the main updates:

  • New: Facebook Pages channel works now on the new permissions "publish_pages, manage_pages".
  • Pending: Facebook Groups channel works now on the new permissions "Group API".
  • Deprecated: Facebook User and Facebook Photo channels, Facebook has deprecated the ability (publish_actions permission) to publish posts to user profiles.

In all cases, Facebook requires declaring the ownership of Pages and the associated domains. Please, plan with time the creation of a site, a Facebook page and the App Review to create a new channel. The current Facebook channels and Apps do not require changes.

  • If you have an App with v2.*, then you can fully authorise your Pages channel.
  • If you have an App on v3 (or superior), or you are approving a Groups channel, then your App must be submitted for App Review. In the meantime, you can start testing with a Test App.

AutoTweet and Joocial 8.20 are available now, compatible with the new permission model; they can be downloaded here.

At this time, we are working on a new tutorial about the new App Review process. The auditory requires to grant access to Facebook to your site and record a screencast to document why you request them the permissions. It is not clear if this is going to be the final procedure once they complete the platform changes.

# Which is the API version of my app?

Which is the API version of my app

# 100 - Graph error: (#100) Only owners of the URL have the ability to specify the picture, name, thumbnail or description params

On November 7, 2017, Facebook released API 2.11, including a restriction to publish only URLs from validated domains. The posts can be published only from the authors who own a Page and an associated domain. No post will be published unless it is published by the team associated with Page, Domain and App.

... link customization is available however the link must be owned by the posting page and a page access token is required. ... See our Link Ownership Guide

To know more about the steps to claim the ownership of a domain, please, visit our Facebook Link Ownership Guide.

# Facebook shows the wrong image, why?

  • REF: Facebook shows a post with a blank rectangle
  • REF: Facebook shows the wrong description, why?

UPDATE: On July 18th, 2017, Facebook changed how the post fields are loaded. Since this date, when you share a link with Facebook API, the value of picture, name, caption, thumbnail, description is taken ONLY from the OpenGraph Tags. This change has already been reported as a bug, for more information: On sharing a URL the picture, name, caption, thumbnail and description set manually is ignored. At this time, it is strongly recommended implementing OpenGraph Tags.

At this time, Facebook ignores the image that AutoTweet defines in the API call and loads the image and other fields directly from the link. Facebook reads OpenGraph Tags and uses these tags to retrieve the page information. To guide Facebook in the choice of the image, we recommend installing and configuring AutoTweet NG OpenGraph Tags plugin. The latest version of the plugin comen with the Smart Generator to generate exactly the righ tags for each link associated with a processed post.

If it is not the image that you expect, it could be the image defined as default image in the general Options configuration.

If Facebook is not able to load the specified Post image, it loads alternative images or a blank rectangle. For instance, a customer has restricted external images access in the internal pages of the site and only allowed access to the Home images. Then, Facebook has detected images from the Home page and included one of them in the Post.

Images must be bigger than 200x200px. These are the recommended image sizes: Facebook Layouts Guide, how to publish Big Pictures. For instance, test with this sample image (https://via.placeholder.com/720x375). For maximum compatibility, remember to use only alphanumeric characters in the file name. Spaces and special characters are frequently a source of problems.

https://via.placeholder.com/720x375

To check these cases, you can test them with Facebook Sharing Debugger. This tool shows how the image is accessed from Facebook servers: https://developers.facebook.com/tools/debug/sharing/

As a reference, Facebook Sharing Debugger output for an image must show the image like this one: https://developers.facebook.com/tools/debug/sharing/?q=http%3A%2F%2Fvia.placeholder.com%2F720x405. If your test does not show the image in the Link Preview, then Facebook cannot load it. In some way, it is being blocked. You can verify any URL, or an image, and get results about how Facebook scrapes your site. It should always get a Response Code 20x and show a Link Preview.

If you have added additional restrictions to htaccess or robots.txt, please, try to restore the original Joomla htaccess and robots.txt. If the problem remains, ask to your hosting provider what can be happening (mod_security?).

# 32 - Graph error: (#32) Page request limited reached

Facebook has applied a rate limit to your account. So, the only way to solve this issue is reducing or distributing the load. For more information:

Particularly, Improving Rate Limits for Page Management Apps

If you are sharing requests to the page between several tools or apps, then it could be hitting the limit.

In any case, we recommend to start checking your Apps following the Facebook Channel Re-Authorization Procedure.

# Facebook Channel Re-Authorization Procedure

  1. Log in to your Facebook Account and remove the App from your Account: Account Settings / Apps and Websites or Business Integrations.

Account Settings / Apps and Websites

Account Settings / Apps and Websites

Business Integrations

Business Integrations

  1. Logout from Facebook. Close your Browser (to finish the session and clear the session cache). Alternatively, you can open a New Private/Incognito Window. Login to Facebook and check that the App is no longer associated with your user account in the Account Settings.

  2. Log in to your Joomla! Backend and authorize the channel as shown in this tutorial.

# Facebook auto post only show up to me when logged into Facebook

Q: I discovered that none of the posts from autotweet were showing up or visible on my Facebook page unless I was logged in as admin. Which is the problem?

A: If Your Own Facebook App is in development mode, only App developers can read the posts. Please, enable it to Live mode.

  1. Go to https://developers.facebook.com/
  2. Click on the Apps menu on the top bar.
  3. Select the particular app from the drop down.
  4. Go to 'Status & Review' from the table on the left side of the page.
  5. Do you want to make this app and all its live features available to the general public? - Select switch to set YES/NO value.

Tutorial: How to AutoTweet from Joomla in 5 minutes

Reference: StackOverflow: The developers of this app have not set up this app properly for Facebook Login?

# I've tested everything with my user, now it does not work on the Live Account, why?

Facebook has reorganized the development workflow to clarify use cases. This step has added new permissions and the way to work and publish content. Facebook has greatly improved to manage administrators, developers and testers.

In the most common development scenario:

  • A Facebook user (Admin) creates a Facebook Page
  • A Facebook user (Administrator) creates a Facebook App
  • In Joomla!, you create an AutoTweet channel, associating the Facebook App and Facebook Page as the content target. The authorization is granted by the same Facebook user.

In the current Facebook user management model, you cannot have separate users for development or production. Now, it is possible to define a development Team in the "Roles" area and testing-specific Apps for your main App. You can manage users and roles, and also define a testing sub-application.

There are other Facebook use cases, besides content publishing, where regular users (not members of your team) can authorize an App with extended permissions. These cases require a Facebook audit and approval.

To sum up, all your users have to be defined under the App "Roles" to define a team (for example your account as an owner is an administrator) and your testing has to be done with a "Test App".

Finally, if you have a multi-vendor site or community auto-posting site (where you do not know your users, they are just registered users - certainly not in your Facebook contacts - ), then you have to apply for Facebook audit and comply with their requirements.

# Twitter Troubleshooting

# 226 - This request looks like it might be automated.

Twitter is not allowing your content to be added to its platform. This message is coming from the new Twitter’s spam protection mechanism. There are several possible causes, for instance:

  • Twitter App is sending the same Tweet multiple times to several timelines.
  • Twitter suspects the account or hosting is possibly compromised.
  • Twitter spam filters may be just rejecting the content itself.

Please, try to reduce the number of Tweets, the target channels, or change the message format for each channel.

TIP

If you are not particularly flooding your timeline with test tweets, then someone in your neighborhood (in the same hosting or IP) might be a spammer. In this case, Twitter has banned the whole server and there is not much else to do.

Ref: Error Code 226 - This request looks like it might be automated

We constantly monitor and adjust our filters to block spam and malicious activity on the Twitter platform. These systems are tuned in real-time. If you get this response, our systems have flagged the Tweet or DM as possibly fitting this profile. If you feel that the Tweet or DM you attempted to create was flagged in error, please report the details around that to us by filing a ticket at https://support.twitter.com/forms.

Filing a ticket at the above URL is the best course of action to resolve any false positives we may be seeing in these detection efforts.

# Couldn't resolve host 'api.twitter.com'

Ref: Operation timed out after 5000 milliseconds with 0 bytes received

Your server is unable to find Twitter API server. This is related to a network issue.

Please, check with your server support if this a general server issue, or it was a temporary problem. If your hosting provider is having problems with the DNS service, then it can be intermittent.

To retry a request, in the Requests list, you can move the Request back to Processed=No, and wait until the next execution to check. In Posts list, you can filter for the specific channel posts and Status=Error, then you can move them back to "Pending" (for manual approval) or "Waiting" (for Cronjob processing).

# Telegram Troubleshooting

# Telegram login failed

Telegram has recently modified the procedure to authorize a Bot to publish into a Channel. Now, it is required to add the bot as a member and administrator to the channel.

Please, follow these steps. In any Telegram client:

  1. Open Channel info (in app title)
  2. Choose Administrators
  3. Add Administrator
  4. There will be no bots in the contact list, so you need to search for it.
  5. Enter your bot’s username
  6. Clicking on it, you make it as administrator.

Ref: AutoTweetNG Joocial: auto-posting to Telegram

# LinkedIn Troubleshooting

# Error Scope "r_organization_social" is not authorized for your application

By default, LinkedIn only authorizes post publishing to personal profiles.

LinkedIn now requires an organisation review to approve apps for company page publishing. For more information: LinkedIn Marketing Developer Program.

If you have not requested the review, then you can only create linkedin personal channels.

# Invalid redirect_uri. This value must match a URL registered with the API Key, why?

The error is caused by any difference or an uninitialized Authorized Redirection URLs field. Have you added all of your URLs in the list of URLs permanently?

Some common mistakes are:

  • You define the Url, but forget to click on Add button
  • http vs https
  • space at the beginning/end
  • www or not www

Ref: How to AutoTweet from Joomla in 5 minutes - Add channel / LinkedIn

# 401 - Unable to verify access token. I got this today, before everything worked, why?

# 401 - Not Authorized

By default, LinkedIn Tokens has a duration of 2 months.

However, in some cases, LinkedIn token expires unexpectedly. The reasons are not clear. The expiration could be caused by:

  • The user has revoked the permission they initially granted to your application
  • You have changed the member permissions (scope) your application is requesting

Additionally, if you change your password, or other software is using the same App, then the token can expire before 2 months.

In some cases, we find that if you access your LinkedIn account frequently, then the token never expires. This is not a written rule, only a finding of our work for some projects.

Please, proceed to reauthorize your LinkedIn channel.

# I cannot authorize, I got "Invalid Redirect URI", why?

Concerning to the second error "Invalid redirect URI", there is a mismatch between your site and your LinkedIn App, please, check this slide:

Add channel / LinkedIn https://docs.google.com/presentation/d/16hGWWGq1IeAZcAkSd8BqnzS2dBDCoC42om6O4bs8gKg/edit#slide=id.gf54ab197_010

Your Authorized Redirect URL must be permanently added to the list and match your site.

# I can't authorize the channel. Error: Could not get access token.

When you authorize the channel and give your approval in LinkedIn, the social networks sends a temporary code to your site.

In the second leg of the authorization, the temporary code is exchanged to the final access token by Joocial. If the extension cannot open a connection to LinkedIn servers, then this error is received: Error: Could not get access token.

Please, ask to your hosting provider is there is any security restriction to call https://api.linkedin.com.

# ... throttling limit for this user/application has been reached for LinkedIn resource

LinkedIn is not accepting more activities from your account. Please, try to reduce your activity to avoid this error, every connected App consumes API calls.

Reference: Throttle Limits, https://developer.linkedin.com/documents/throttle-limits

# Google Blogger Troubleshooting

# Invalid field: Access token / Error fetching OAuth2 access token, message: 'invalid_client'

Please, remove JavaScript Origins from Client ID or Referers from Key for browser applications, and try again. It must be none and Any referer allowed for each one.

TIP

You do NOT have to write anything and Any referer allowed in the fields, you have to clear these fields, removing any entered value.

Your Client ID and Key for browser application must exactly match this slide:

Tutorial: Publishing to Google Blogger / How to configure

TIP

The domain must be exactly the same back-end URL. www... does matter, if there is a minor difference, even just www, it is a whole different security domain.

Additionally, check if you have copy-pasted additional spaces, for instance in the Client Secret field.

Finally, make sure that you have following APIs are enabled in https://console.developers.google.com, under "APIs":

  • Google Blogger API
  • Contacts API (just in case, it is not always required)

Ref: Google Blogger - What are the steps to authorize the channel?

# When I try to authorize the Google Channel, I receive a "redirect_uri_mismatch" error, why?

The error is caused by any minor difference in the App Redirect Uri definition. For example:

  • http vs. https
  • space at the beginning/end
  • www or not www

Please, delete the channel, remove the App from your authorized Apps (https://plus.google.com/u/0/apps), access your site with a different browser (or with a Private Tab), recreate the channel and try to authorize it again.

# Plug-ins

# I have updated to a new version, and an AutoTweet integration stopped working

AutoTweet includes a component, modules, core plugins, and optional plugins. AutoTweet component, modules, and core plugins are updated by Joomla! Extensions installer. But, AutoTweet optional plugins, which are manually installed, must also be manually updated following the same procedure.

After an AutoTweet update, please, verify if you have installed the latest version of the optional plugins. You can find them in the same AutoTweet version package UNZIPME-autotweetng-.....zip.

You can also check the latest versions in AutoTweet / System Check, or in the Compatibility Chart for AutoTweetNG and Joocial.

# I have installed the plugin without error but nothing gets published ...

Please, check the content flow:

  1. Plugin: Is the plugin activated? Have you enabled any plugin filter? Please, try to disable them just to check.
  2. Request: are they processed? Are they waiting?

Q: There are requests on the list, waiting to be published, but they are not delivered, why?

  1. Rules: Have you created rules? Please, try to disable them just to check if they are affecting the processing.
  2. Posts: are they published into the channel?

If these basic tips do not solve the issue, please try to enable the logging mode to inspect the internal processing.

In any case, if you cannot solve the case, please, send us the logged file to our support service to review it.

# General Troubleshooting

# Deprecated notices in the extension output

  • Warning: "continue" targeting switch is equivalent to "break"
  • Deprecated: Function create_function() is deprecated in ...

The warning messages are generated from PHP to ease the transition to PHP 8. We are already working on the next major version to support the upcoming Joomla 4 and PHP 8 (Q4 2020-2021).

In the meantime, you can disregard the messages and disable the maximum error reporting of the site. These messages are only shown when the development mode / maximum error reporting is enabled.

On live sites, it is generally recommended to set "Error Reporting" (Global Configuration/ Server) to "None". This setting avoids any notice on your site and hides internal information. This setting doesn't affect the installed extensions.

# Channel manager only shows a "loading" message

Error message: "loading" or "Requesting channel data"

There is an HTML/JavaScript error caused by a site misconfiguration or a security restriction on your site.

The channel manager loads the channel type sub-form with an Ajax query to your back-end site. If the form cannot be retrieve, the "loading" message is not replaced by the right sub-form.

There are several hosting issues that can generate this behavior:

  • Directory Permissions, check if Joomla! directory permissions are Writable (System/System Information/Directory Permissions). Particularly, media/lib_extly/tmp directory.
  • JavaScript errors, if there is any JavaScript error, the form load is not going to be completed.
  • HTML errors, your site does not have a valid HTML body structure. Please, try to locate the source of the invalid HTML page.
  • Advanced optimization techniques, several layers of compression can interfere with JavaScript and Html code. Please, check your hosting configuration to discover the problem source (disabling one by one). For instance, CloudFlare, PageSpeed, RokBooster, etc.
  • Security restrictions, if there is a restriction to back-end Ajax queries, then connections are not going to be successfully completed. For example, mod_security can disable this queries, please, try to disable mod_security or any other security mechanism temporarily.
  • JomSocial Azrul's plugin adds a JavaScript routine to the whole site. Please, try to disable this plugin.

In addition, you can inspect your browser console to discover if there is a JavaScript error behind. Press Control-Shift-J, and access the page to discover any HTML/JavaScript error.

References

# Feeds

# Articles from RSS feeds are not detected, why?

Q: I have an extension that imports articles from RSS feeds, but AutoTweet does not see those posts. Is there a way to make it so autotweetng will post all new articles regardless of how they are created on the site?

A: AutoTweet detects the new articles, but they have to be published and within a certain date range. Are you importing articles with the today's date or older articles?

Please, try to adjust the Polling window (hours) to load older articles (Control Panel / Options / Advanced Settings / Content Polling Settings / Polling window ), by default it is defined as 24 hours window.

# Error: A feed could not be found at ... A feed with an invalid mime type

This error is found when the RSS library cannot process and parse the Feed type.

Please, double check the RSS Url, or try to load it with a different RSS reader.

The RSS Url must be a valid XML. You can check it with https://validator.w3.org

TIP

If you are sure that the RSS Url is fine, you know what the source site is generating it with Joomla and the site has Admin Tools, please, disable Malicious User Agent block (MUAShield). (WAF / Active Request Filtering). More info about the issue, #26809 – MUA Shield blocking Simple Pie requests.

# System Check

# The System Check is showing a red timestamp difference, why?

A timestamp difference signals that your server clock is not updated. Facebook, Twitter, etc are not going to accept your server-side OAuth authentication. Please, check with your hosting provider to update the server clock.

TIP

In System Check, if the timestamp difference is a small, less than 10 seconds, then it should not affect the OAuth authentication. It may be caused by server virtualization or networking delays.

Server timestamp is not related with Joomla! time/timezone or User timezone. Server timestamp is universally defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970. Unix time is not defined according to time zones. Read more, https://en.wikipedia.org/wiki/Unix_time.

# The System Check is showing a red Timestamp difference (998), why?

Concerning to Timestamp difference (998), you have disabled "Version check (Offline mode)" (Control Panel / Options / Live Update tab). In this mode, Timestamp is not checked and it just shows 998. Please, try to enable it again just to check your site Timestamp.

# The System Check is showing a red Timestamp difference (999), why?

Concerning to Timestamp difference (999), AutoTweet is unable to verify the timestamp. AutoTweet opens an external connection to verify the server time. Particularly, it opens a secured SSL connection, via cURL module, to Twitter servers. Please, check with your hosting provider if there is any restriction or misconfiguration to perform this basic action.

# Installation - Upgrade

# Tried upload and got this error message: Parse error: syntax error, unexpected T_FUNCTION

You are running an outdated version of PHP (not stable), which is not supported by the extension. Most hosting providers already offer to upgrade to PHP 7.2.

Please upgrade to PHP 7.1 or later as soon as possible (previous PHP versions are not longer considered stable. They don't have Bug fixes, Patches, or Security issues fixes).

# Live Update does not work; Update path does not exist

Joomla! shows this error message when you try to update to the extension latest version.

Live Update does not work, Update path does not exist

Joomla! cannot successfully download and install the file.

Have you assigned the Download ID? It is required to authorize downloads.

  1. Please, click here to access your Download ID.
  2. Copy and paste Download ID into component Options/Live update/Download ID field
  3. Update from "Extension Manager: Update"

If the problem persists, we have found a minor incompatibility in the latest Joomla! installer plugin, please manually download the extension and install it to update the installer plugin and the rest of the associated files. Next time, it will be updated with no errors.

# Cron created but no processing, why?

To verify if the Cron job command is executing, please, enable the logging mode and check if log entries are recorded following the defined interval.

If no records are added after a while, then it is not executing.

In general, we recommend to execute the Native CRON script, but there are also many alternatives.

Since every hosting platform has its own settings, please, ask your hosting provider what is the best way, check hosting documentation or send them the command script to verify it. Sometimes, the command line requires additional permissions or a slightly different command.

# Executing in Cron job mode, posts have this domain-error-running-as-cronjob.com/home/... URL, why?

When you run Autotweet in a command line context, there is no way to know the real URL domain. Base URL Override parameter must be defined to create the right URLs.

# General

# My system shows a Blank White Page. What should I do?

A blank white page is an error page!

Due to PHP errors, AutoTweetNG or Joocial (or any other Joomla extensions) can stop working without displaying an error, just a Blank Page. The Blank Page is caused by disabled PHP Error Reporting. This is a common security measure in production sites.

Again, a white page is just an error page where the error message has been suppressed by your configuration. Once you solve the error, the site is going to be back to the normal state.

In these cases you have to enable PHP Error Reporting to find out what the error behind the white page is:

  1. Check your server error logs (not the access logs): even when PHP Errors are disabled, they may be saved in an error log file.
  2. Joomla! Configuration - Error Reporting: go to Joomla! Administration / Global Configuration / Server, and enable "Error Reporting" to Maximum.
  3. If your site still shows a Blank Page, your hosting provider may have restricted this setting too.
  4. Additionally, if you can't access the back-end website, check the next cases.
  5. Hosting Configuration: visit CPanel, or your hosting control panel, and try to enable PHP Error Reporting in this area.
  6. Alternatively, you can ask to your Hosting Support, how to enable it.
  7. PHP Configuration: enable display_errors to "on" in php.ini

# A solution for 80% of Blank White Pages

You have installed an extension (package). Joomla! is trying to load several new system plugins, a dependency is not fulfilled or there is a PHP Error on your site.

  1. If the front end website is down, Joomla! backend may work (it does not load the same plugins). Please, try to access the backend to disable the latest installed "system" plugins.
  2. If the Joomla backend is also down, access your Database and manually disable the latest installed plugins.

For example, to review the latest installed plugins from phpMyAdmin/MySQL:

To disable a plugin, change the enabled column to 0.

# What can I do to get my system back, if the white page persists?

There is an alternative way to avoid a system plugin load, but it requires to access directly to website files and remove some of them. Please, proceed with the following steps:

  • Access your site directory, for example via FTP
  • Rename the latest installed system plugins folders in "[Joomla_root]/plugins/system/"

# Next time

We develop and test our extensions to minimize conflicts and installation problems. However, we can't preview all environments and extensions combinations. It is also common to find very restrictive or very resource-limited hosting platforms. To avoid this problem, we recommend:

  • Always, test new software on a development site.
  • Always, create and check to have a recent backup at hand (test how to quickly restore it). Akeeba backup is a great component, and very easy to use.
  • Always, if you are going to install it in your live/production site, install it at a convenient time (Eg weekend). You can also announce a downtime window to upgrade your site, and be ready for a rollback.

# Logging Mode: Developer's swiss army knife

The Logging Mode is a key tool to check the extension inner workings. It is a handy way to check component internals, beyond a simple error message.

You can enable several logging modes to leave a track of server-side operations.

To enable the Logging mode:

  • Access the Options menu, in Components/(Extension Name) Control Panel.
  • In the System Settings folder,
  • Enable the: Logging level (For example, 3-All)
  • And, select the Logging mode (For example, To logfile only or To logfile and screen)

Logging Mode: Developer's swiss army knife

As a result, xt-logging.log file is generated with all operations details into logs/ directory. Please, check the file generated in logs/xt-logging.log.

TIP

To check in full detail how it is executing, you can just enable the Logging mode to show 3-All To screen only, and manually Process requests or Publish Posts.

xt-logging.log can be downloaded from System Check.

System Check - xt-logging.log