WordPress Akeeba – Ajax Loading Error

I was restoring a WordPress website using Akeeba kickstart in my WAMP environment. I got the following error.

I moved over to XXAMP I got site installed; however, my SendMail isn’t set up in XXAMP so I couldn’t test the forms. I wanted to restore the site in WAMP.

Ran the Akeeba Kickstart again and this time I choose to run the files restore “directly” and “ignore most errors”.

The website installed, but while working on the site I discovered a lot of odd things. None of my Widgets or Widget positions were available in the dashboard.

I ran the install again, but this time I did not check “Ignore most errors”. This is installed correctly this time.

I hope this helps someone else out there…

 

Best WordPress Backup Solution – Akeeba

I have used Akeeba for years for Joomla and made moving and backup up sites so easy. I started purchasing the Pro version so I could exclude various directories and back up to Amazon Web Services. With the use of a Cron Job my sites were taking care of themselves.

I was so glad to see Akeeba make their backup solution for WordPress. The best part was the way it ran the 3 SQL statements you need for updating the permalinks automatically. Although this was best solution I had used for backing up and moving a WordPress site it didn’t always work. Sometimes it would never finish running the SQL permalink updates and the site wouldn’t complete the move. In addition, the plugin would tell me I had an update available, but when I tried to automatically update it the site was breaking. I would end up with a blank white website.

Well this latest version of Akeeba Backup / Kickstart software is working really well. When ever I have moved a site the Permalinks update works well, and the latest version updates through the plugin manager without a hitch. I would highly recommend this software to anyone. The pro version is totally worth it.

I hope this helps someone else out there…

 

Install Joomla Akeeba Pro – Automated Backups

I have done this before; however, some times you need a re-fresher. I started with Localhost version. My Local Environment is Windows 7 running WAMP.

I used “Task Scheduler” to be my local Cron service.  I start by right-clicking on the Task Scheduler and “run as administrator“.

  1. Create a task

  2. On the General tab give the job a name so you can identify the task. I checked to “Run whether user is logged on or not“. Do not check “hidden“.
  3. On the Triggers tab click “new“, and set the time you want this to run. I checked to “Stop task” if it is taking longer than an  hour.

  4. In the Actions tab click “new”, and for the Action select “start a program“.  Browse to your WAMP and locate the PHP.exe. For the arguments add the full path to your sites “cli” folder. Mine is “C:\wamp\www\mywebsite\cli\akeeba-backup.php”
  5. The next tabs Conditions and Settings are self explanatory.

Live Site

  • Shared hosting with Godaddy
  • Joomla 3.8.6 site
  • Akeeba 5.5 pro

I needed to get my path to my PHP.exe with the Godaddy shared hosting and the configuration wizard totally figured this out.

/home/mycpanelusername/public_html/cli/akeeba-backup.php

For the PHP path I used

/home/mycpanelusername/php

The path I used for the PHP was no good. I found the next article on Godaddy’s site.

https://www.godaddy.com/help/create-cron-jobs-16086

/usr/local/bin/php -q /home/[user name]/[path to the file]

https://uk.godaddy.com/help/what-is-a-cron-job-3483

I used the following video from Akeeba to get it right.

https://www.akeebabackup.com/videos/1213-akeeba-backup-for-joomla-pro/1623-abtp02-automating-backup.html

My Final path was:

 /usr/local/bin/php /home/myaccount/public_html/cli/akeeba-backup.php

When I ran the configuration I was given the correct path to the Akeeba-backup.php file.

In the CPanel hosting I went to “cron job”, and created a job.

I hope this helps someone else out there.

Disable or turn off Akeeba Backup Before Updating Joomla

I needed to update to Joomla 3.7 and every time I did it ran an Akeeba backup. I already ran the back up before I started, so I just wanted to update the Joomla core.

You can do this by go into the Administrative area >> Extensions  >> and Plug-ins. Look for “System – Backup on update” and uncheck it.

This article helped me solve this.

https://www.akeebabackup.com/support/akeeba-backup-3x/Ticket/22374-disable-backup-before-updating-joomla.html

I hope this helps someone else out there…

 

I recently updated virtumart in a Joomla 3.6.5 site and got the following error.

1054 Unknown column ‘product_stockhandle’ in ‘field list’ SQL=UPDATE `#__virtuemart_products` SET `virtuemart_vendor_id`=’1′,

It was longer than that, but I needed to fix the site so I don’t the rest would help. I could be wrong.

My last back up was too long ago. I was kind of screwed.

I restored the backup in a close directory on the production server. It was on https so I couldn’t do it localhost. I exported all the virtuemart tables in one MySQL statement by selecting “custom” when exporting. I did have to move the images/stories/virtumart directory. After that the store was operating normally. I made a backup before doing anything else.

I  used FTP and copied the components/virtumart directory over to the site that had issue; however, this didn’t fix the issue. Not sure what broke.

I hope this helps someone else out there…

 

 

Akeeba For WordPress – Kickstart AJAX Loading Error 500

Moving a customers WordPress site to a new hosting plan I ran into this error.

This turned out to be an semi-easy fix. The website size was too large for the hosting. Well not really; however, Akeeba requires 2.5 times the size of the site to fully extract the site.

I looked at the website files to see where I could trim some fat. The site was 400 megs.  There was a folder called “wp-snapshots” which held a backup. I removed all the extraneous files including my first Akeeba backup. Made a new backup which was only 40 megs. This time when I ran Kickstart the site installed without an issue.

I hope this helps someone else out there…

 

Akeeba Backup In Joomla 3.6.2 To 3.6.4 – ERROR: The archive file is corrupt, truncated or archive parts are missing

I was struggling with this issue of upgrading a 3.6.2 site on a WAMP / localhost install. I would select to upgrade, Akeeba backup ran, the upgrade would crash with percent done as “NAN” or “not a number”.

joomla_3_6_4_akeeba_fail

The fix was the “tmp” path and manually install patch. For a localhost install the path needs to have both “\” for the local part and “/” for the server part of my machines environment.

joomla_3_6_4_path_fix_log

joomla_3_6_4_path_fix_tmp

I wasted hours on this. I should have checked another localhost install sooner.

The other part was to go into Components >> Joomla! update >> and this time do a manual “Upload & Update” process. You will need to download the 3.X to 3.6.4 upgrade and install this.

Before I could upload the package I was warned about two PHP.ini settings of post_max_size and upload_max_filesize had to be the same. I set them both to 128m.

Before I ran the update I removed Akeeba so it wouldn’t run another backup before the upgrade, but I learned when I went into Extensions and Manage that I could just select and choose “disable”.

I really hope this helps someone else out there…

 

 

[Solved] – Joomla log into administrator area – Fatal error: Class ‘FOF30\Container\Container’ not found

My local version worked perfectly; however, when I tried to log into the administrative area I got the following error.

Fatal error: Class ‘FOF30\Container\Container’ not found….

This article helped me to get started.

https://www.akeebabackup.com/support/akeeba-backup-3x/23141-fatal-error-in-administration.html

Basically I deleted the directory “plugins/quickicon/akeebabackup”. I was then able to access the administrative area again.

 

I hope this helps someone else out there….

 

Joomla 3.6.2 – The most recent request was denied because it contained an invalid security token.

When the Joomla 3.6.2 update finalizes I get the following message.

The most recent request was denied because it contained an invalid security token. Please refresh the page and try again.

I just delete out everything in the URL after “administrator” and hit refresh.  I can’t wait till this gets fixed. Have to admit I am disappointed with this last round of Joomla updates.

The next site I started the upgrade. I use Akeeba so it ran an Akeeba backup, and then gave me the error.  When I cleared the the stuff in the URL after “/administrator/” the site said I still needed to update to 3.6.2.

The site was telling me to update other components so I started with upgrading Akeeba from 5.1.3 to 5.1.4.

After I updated Akeeba to 5.1.4 and tried the Joomla update the update installed correctly.

I hope this helps someone else out there…

 

Joomla 3.6.2 update – Email Cloak Fix

Another Joomla! update just two days after the 3.6.1 update. It is getting stressful to stay on top of all these update and the pitfalls one can encounter.

Here are some tips I have come across this morning.

Joomla – https://docs.joomla.org/J3.x:Updating_from_an_existing_version

JoomlaShack – https://www.joomlashack.com/blog/tutorials/361?utm_source=Alledia&utm_campaign=a0292c0a93-The_Alledia_Newsletter&utm_medium=email&utm_term=0_80803af9fd-a0292c0a93-270714557&goal=0_80803af9fd-a0292c0a93-270714557&mc_cid=a0292c0a93&mc_eid=bb80f31be3

I have updated a few sites this morning and had no real issues. I did have to do the following to get everything to work.

  • Go to Extension > Manage > Database.
  • Click “Fix”.

I had to upgrade my Akeeba to 5.1.4 on one site first before the update worked.

This brings about the question of how much to charge customers to keep the site up-to-date. That will depend on how much you charge per hour and how complicated the site is to review to ensure the upgrade didn’t break anything. Here are some things I am putting into considerations.

  • Time it takes to upgrade( 30 minutes ) I timed my 3.6.1 update to 3.6.2. It took about half a hour to update Akeeba, run the Joomla update, clear the cache and quickly check the site.
  • How many Joomla Updates per year – ( 10 times per year ) I wasn’t able to find this out directly, but another site that did a comparison on CMS’s stated that every 31 days is Joomla’s update cycle, so roughly 10 updates per year. That brings us to about 5 hours per year in just updating the Joomla! core if nothing goes wrong.

I hope this helps someone else out there…