Post Gopher Error Messages

Below are common error messages encountered when using PostGopher and the best way to resolve the issue

The uploaded file exceeds the upload_max_filesize directive in php.ini





















This error is due to the limitation put in place by your hosting provider. Many providers set the maximum upload file size at 2MB and the PostGopher zip is 2.5MB.  You can contact your hosting provider and request to increase your maximum upload file size

TCPDF ERROR: Please explicitly set action attribute path!






















This error is occurring because your content on that page/post has an HTML form embedded as part of the content and this post does not have the action attribute set.  It may be caused by a conflict with another plugin that supplies the form.  We suggest you deactivate that plugin and give it a go to see if the error goes away.

TCPDF ERROR: Could not include font definition file: ...





















This error means you are using a font not supported by PostGopher at the moment.  Please change it or/and contact the customer happiness team to request it be added.

TCPDF ERROR: [Image] Unable to get the size of the image





















This is down to the PHP configuration on the server. You need to get your hosting provider to enable fopen wrappers in PHP. They should know what that means!

Parse error: syntax error, unexpected ':'






















This error occurs when your hosting is not running your site on PHP 5.6 or above.  Please check with your hosting company.

AWeberAPIException: Type: NotFoundError; Msg : Object: None, name:





















Once you have entered your Aweber Authorization code you must click SAVE.  When the page refreshes, you can select a list from those in your account.  This error code indicates that you have not done this.  

Fatal Error undefined function mb_convert_encoding()





















You need to ask your hosting company to insure that the  mb string PHP module is installed.  Normally it is but if you encounter this error ... that is the reason!

cURL error 35: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error




















This error occurs when your hosting is not running your site on PHP 5.6 or above.  Please check with your hosting company.

cURL error 7: couldn't connect to host


















Please check with your hosting company to make sure that access to external domains is not restricted or that a firewall is not blocking access. Some hosts, such as Amazon AWS, do not allow certain plug-ins - and sadly Post Gopher gets caught in their net.

There was a problem with the HTML Signup Form - Could not find input buttons. 
Please try another HTML Form

For every optin form there must be at least the field to gather the email, and the SUBMIT button. Normally there is also the name field. An example is shown below.  Note the 

  1. <input name="name".... > 
  2. <input name="email".... > 
  3. <input type ="submit".... > 
<form action="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx">
<input name="name" placeholder="Name" type="text">
<input name="email" placeholder="Email" type="text">
<input name="form_id" type="hidden" value="2">
<input type="submit" name="submit" value="submit">
</form><br>

Fatal error: require_once(): Failed opening required ‘/home/xxxxxxx/public_html/wp-content/plugins/postgopher/TCPDF/tcpdf.php’ (include_path=‘.:/usr/local/php71/pear’) in /home/xxxxxxxx/public_html/wp-content/plugins/postgopher/includes/class-post-gopher.php on line 191

The site is experiencing technical difficulties.
This is due to a file going missing. This can happen if the plugin did not install correctly. Please deactivate and then delete the Post Gopher plugin then re-install. If you then still get the same error, it is possible that an Anti Virus program on your server is removing it, so you need to speak to your hosting company to make sure this is not happening.

If you reinstall and find that Post Gopher works for a short while then fails again - this is a definite indicator that the hosting company Anti Virus program is removing it on a subsequent scan 
Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/xxxxxx/public_html/wp-content/plugins/postgopher/TCPDF/tcpdf.php on line 17782
Warning: Cannot modify header information - headers already sent by (output started at /home/xxxxxxxx/public_html/wp-content/plugins/postgopher/TCPDF/tcpdf.php:17782) in /home/insanelygood/public_html/wp-includes/functions.php on line 6029
Warning: Cannot modify header information - headers already sent by (output started at /home/insanelygood/public_html/wp-content/plugins/postgopher/TCPDF/tcpdf.php:17782) in /home/xxxxxxxxx/public_html/wp-admin/includes/misc.php on line 1252
Warning: Cannot modify header information - headers already sent by (output started at /home/insanelygood/public_html/wp-content/plugins/postgopher/TCPDF/tcpdf.php:17782) in /home/xxxxxxxx/public_html/wp-admin/admin-header.php on line 9

All or any of these implies that the server is set to development mode and not production. So not only do these warnings show but the whole PHP / WP setup will be slower than usual for being set this way.  Warnings like these are only meant to be shown in development servers, so developers can get heads up about potential issues in future versions of PHP.  So for example the warning shown is saying that this particular statement will be changing in a future version and so the developer will need to look at and make changes before then, which is usually 6-12 months in the future.

You should contact your hosting company and get your website in to production mode. Then a) these warning won't show and b) your site will be faster and more secure.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Related Articles