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.
When developing desktop applications that interacts with Facebook you have to implement the login flow your self. After the login flow completes you can use the normal Facebook SDK libraries by supplying it with the access token your received. When implementing the login flow you have to make sure that you receive the access you requested. You can get a partial approval by the user and not be able to access all the scopes you need. In this example I have implemented the Facebook login flow into a C# .Net desktop application. Full source is available for download.
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.
During my professional career as a developer most of the time I have been using Team Foundation Server (TFS) for source control. Back in the day I even used Source Safe, stone age history for most people. For my private project or small startup projects "the files on disk with occasional zip backups" approach has been way to common. I have also used different GIT solutions as well as Google Code. It works fine but when you are use to TFS it's not as easy as you are use to. All the mayor cloud suppliers want to flirt with the startup community by offering free services that will keep the startups close when they grow bigger. We have seen several examples of this from Microsoft in the past, like BizSpark. Now they offer free Team Foundation Server in the cloud called Team Foundation Service or Visual Studio Online. The basic account is free for up to five users with unlimited repositories. Support for both TFS and GIT repositories!
So far I have added two of my current projects and the performance is really good! There is also many ways to extend the service with your own code and REST APIs. You can also use free resources for builds, load testing and more. If you require more resources they can be purchased on a pay for what you use approach. If your project grows you can add additional team members for $20/month.
I decided to break the RAID1 on my Dell M6500 so I could run Microsoft Server 2012 R2 along with my Windows 7 installation. When the RAID was deleted I thought it would be best to switch my SATA controller over to AHCI since I'm running two Corsair Force GT SSD drives. After changing to AHCI the computer blue screens during boot. I have done it several times before but not often enough to remember what needs to be enabled. This behavior is documented in Microsoft KB922976 (Error message occurs after you change the SATA mode of the boot drive) with automatic registry fix and all. However this is not the complete solution for all situations.
According to the KB you need to enable loading of the AHCI driver, a no brainier! And also enable the Intel AHCI controller driver. But what is not included in the KB article is that the ATAPI driver also needs to be enabled for it to work. If you try to change from ATA to AHCI it is already enabled, if your computer booted with the ATA setting.
So according to the KB you should set these two registry keys to "0":
But you should also check that this one is set to "0":
You can also run these commands instead:
REG ADD HKLM\System\CurrentControlSet\Services\msahci /v Start /d 0 /f /t REG_DWORD
REG ADD HKLM\System\CurrentControlSet\Services\IastorV /v Start /d 0 /f /t REG_DWORD
REG ADD HKLM\System\CurrentControlSet\Services\atapi /v Start /d 0 /f /t REG_DWORD
Now your computer will start without the blue screen!
Facebook like button, follow button, like boxes, fan pages and application. Which one should you use and why? For blog SEO social media is important both for users to share your content as well as informing your readers about new posts. Facebook have made a lot of changes since they first introduced the like button. In this article I will try to explain how it all works.
A social media update that includes an image will be clicked much more then one without. Most updates today includes thumbnails to make the update more attractive for the end-user. When a blog, or other web site, shares content via share links or automatic updates the receiving site uses different methods to draft up the update layout. Most sites use the Open Graph protocol to do this, and the implementations differs a bit from site to site. LinkedIn however makes different implementations each time it seems.
Before you start doing any search engine optimization (SEO) work on your site you should implement tracking on your site. If you don't track events on your site you will not be able to target your SEO efforts and follow up on the results. If you haven't read my SEO Basics post you should take some time and do that. In that post I talk about tracking in two different ways, both tracking your visitors (or traffic) as well as "tracking" your site content behavior via Google Webmaster Tools. In this post I will explain more about the tracking part of SEO.
So the new issue on the board is shellshock? Not really it has been around for 20 years but hasn't been a problem until now. Same with heartbleed, was there for over two years before it was discovered. I will show you how to check if your effected and how to stay safe.
The heartbleed vulnerability dropped like a bombshell, a large majority of web servers on the internet was sharing there memory with the world. The even bigger bombshell was that the vulnerability had existed for over two years. Most people consider open source more secure then proprietary code since anyone can verify that it's safe. The problem is that most people think that someone else already done that!