I have been using WordPress Download Manager for a long while. I have never been happy with it but the latest update just makes me cry! If you haven't upgraded yet, don't do it! If you already upgraded you probably ran into the same problems I did.
All downloads gone - You have to go into the "Settings" page and migrate all your download packages.
All download icons are gone -Nothing more to do then go into each and every package and select a new icon.
Short codes like [wpdm_tree] doesn't work anymore - From now on you have to use a plugin, WPDM Extended Short-codes, for this. It isn't available in the plugin repository. You have to download it and install it manually.
All the links to your download list generated by [wpdm_tree] returns 404 Not found - This is true for both migrated downloads as well as new ones. This is probably because the new version uses custom post type instead of linking to the actual file. It works fine in preview but doesn't work live. This probebly has to do with permalink structures and so on, obviously not tested properly before release. I figures out that I had a regular post for each download with the link at the bottom so I just edited the permalink for each download to the same slug as that page. The result is that the user is sent to the post with the download link at the bottom that actually works.
I have been thinking about founding a new solution for my downloads for a while and now that time table was just pushed up! I hope some of this information helps you get through some of the problems.
Your website needs to be publicly accessible to use Jetpack: site_inaccessible
Error Details: The Jetpack server was unable to communicate with your site https://www.hackviking.com [IXR -32300: transport error: http_request_failed SSL certificate problem: unable to get local issuer certificate]
If you receive the error message above when trying to connect jetpack for you WordPress site there is a small problem with your SSL certificate. This is because the wordpress.com server are unable to verify your SSL certificate chain. Your certificate is signed with an intermediate certificate from your supplier. Your server should supply that intermediate certificate but if it doesn't your browser already have the mayor intermediate certificates and can solve this issue it self. However wordpress.com can not take care of this if your server doesn't supply the intermediate certificate package.
To solve this you should install the intermediate certificate package supplied by your CA on the server. If you don't have that kind of access to the server there is a work around to get jetpack up and running.
In your wp-config.php find
and replace it with
Make sure you log in to the /wp-admin without https and then connect jetpack to wordpress.com. Now you can change the FORCE_SSL_ADMIN line back to true and it will all work.
Running WordPress on Google App Engine is possible but different from any other hosting you ever used. Stability and performance are really great but it comes at the price of flexibility. In return you get a highly scalable and robust solution for your website. After running a few months on Google App Engine platform I switched again and in this article I will tell you why.
Why not run WordPress on Google App Engine? You will get performance and stability while only paying for the resources you actually use. Reading the official Google tutorial "Running WordPress in App Engine" it gives you a fare idea what you are in for. But if you want to migrate a currently running site then you have to do some tweaking. So here is a run down on how to do it!
Ever got this error:
Warning: Cannot modify header information - headers already sent by
(output started at /storage/content/52/102452/hackviking.com/public_html/wp-config.php:1)
in /storage/content/52/102452/hackviking.com/public_html/wp-includes/class-wp-ajax-response.php on line 129
I Googled it a lot. Got number of posts on the problem. Almost all the posted solutions was about blank spaces and unclosed php tags (?>). I tried it all. Worker through all of my template files and got nothing. Removed the template and still had the issue. Checked for blank spaces in the wp-config.php file and still nothing worked. Then I found that the wp-config.php file was Unicode. Re-saved the file as ANSI and re-uploaded it via ftp and it was all working again.
Had some problems when I installed the Feeds Locations plugin in my wordpress blog today. Installation was fine but when I tried to activate the plugin I got "Plugin has invalid header" error. My other blog have the same plugin and it works fine, both blogs is version 3.0.1. The plugin didn't show up in the plugin editor either but I got it running with a quick fix.
- FTP in to you site and goto /wp-content/plugins/wp-feedlocations/
- Download the zip-file with the plugin and extract it.
- Upload the .php file.
- Edit the readme.txt, change the row "Tested up to:" to your current version.
Now the plugin shows up when you refresh your admin page and you can activate it.