Support

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

Hi Akeeba folks,
When updating Akeeba to 3.10.1. I got the following message: "Temp directory is the same as the site's root". Because of that Akeeba Backup does not work anymore. Unfortunately, I'm not able to fix that issue on my own. Under the rubric "How to fix this issue" it says "search for SCRIPT_FILENAME". But what exactly do I have to do to search for SCRIPT_FILENAME?

And where can I find this "/home/users/myuser/public_html/administrator/index.php" in order to replace /administrator/index.php with /tmp?

I've googled, but all information resulted in nothing.

Could you please help me to fix that?
Thanks in advance
Best regards
Tim

The backup log that you attached is for a successful backup. I assume that is from before this problem started?

Let's check the easy stuff first. In your Joomla! Global Configuration file, check the path for the tmp folder. It will be a fairly long path because it starts at the server root. It should end in the "tmp" folder in the root of your site. If it ends at the root of your site with no tmp, then add the tmp folder to the end. Now make sure that there is a tmp folder in the root of your site using FTP or your host's file manager. Try your backup again.

If that is not the problem (the path ends in tmp) then your PHP is set up with the PHP temp folder pointed to the root of your site. Please ask your host to fix this problem and make it point to a specific folder. The instructions that you were reading don't work with all hosts, many of them block the techniques to modify the PHP setup.

Hello Dale

Thanks a lot for your valuable help. You are very right: I need to ask my host to get things sorted out. I'll let you know about the outcome asap.

In the meantime

Best regards

Tim

You are welcome!

Hello Dale

I have good news. I could fix the issue. My host provider was very helpful. Thanks again for your support.

May I please ask you another question?

Akeeba also allows only a main site database backup. Then, under "Advanced configuration" one can configure the size for split SQL dump files. I chose "Custom ... 2.00 Mb", clicked on "Save", then on the "Backup Now!" buttom. But unfortunately, the generated sql File had a size of 6.0 Mb - the full size of my database! So there was no generated split! I expected 3 automatically generated SQL dump files of a size of 2.00 Mb. Do you have any suggestion to make this happen?

Best regards
Tim

You almost had me on that one! With a database only backup, there is no archive, the output is a sql file. The split setting only applies to splitting the archive file. The file type has to be zip or jpa.

Depending on what you are trying to do, the All configured databases (archive file) may suit your purposes.

I'm glad you got the temp setting worked out!

Hi Dale,

Thanks for your comment.

Basically, I'm trying to transfer my Joomla site from a live web server to localhost using Akeeba Backup. Everything has gone fine except when using the Jomres Inegrated search feature (clicking on the Search button) I get this message:

Not Found

The requested URL /index.php was not found on this server.

apache_error.log:
[Mon Feb 24 22:47:18 2014] [error] [client 127.0.0.1] script 'C:/wamp/www/index.php' not found or unable to stat, referer: http://localhost/joomla/index.php?lang=en
[Tue Feb 25 00:02:20 2014] [error] [client 127.0.0.1] File does not exist: C:/wamp/www/wpad.dat

Any idea what could be the reason for that? How can I fix it?

Best regards
Tim

If you have used .htaccess Maker on your live site, you would need to regenerate the .htaccess file for the local server. I realize you're only transferring the database, but if you previously transferred the .htaccess file, that could be the problem. You would need to change the site URL at the bottom of the .htaccess Maker screen.

If your site is displaying strangely, no css, 404 errors on your menu items, etc. then it is something else. I don't think this is the problem, so I'm not going to go into detail on how to fix it.

Hi Dale,

As an enthusiastic learner I've tried quite a lot.

>>If you have used .htaccess Maker on your live site, you would need to regenerate the .htaccess file for the local server.


How can I use this .htaccess Maker on my live site? I installed Akeeba Admin Tools Core 2.6.0, but there is no .htaccess Maker available! I think, this could be the key to fix the issue.


The nitty-gritty: When using the Jomres Inegrated search feature (clicking on the Search button) the frontend root http://localhost/joomla/index.php?lang=en changes to http://localhost/index.php?option=com_jomres&arrivalDate=25%2F02%2F2014&departureDate=26%2F02%2F2014&country=All&ptype=All&guestnumber=0&send=Search&calledByModule=mod_jomsearch_m4&Itemid=1209

I've goggled and noticed that on localhost the URL rewriting has to be switched off. I also tried to comment out
Options +FollowSymLink
by adding # in front of: Options +FollowSymLink
in .htaccess, but no luck!
In this way the RewriteEngine must be On!

>> I realize you're only transferring the database,

It's all about a complete transfer of my Joomla site from a live web server to localhost. Also, this Akeeba User manual helps to understand this fairly new matter.

https://www.akeebabackup.com/documentation/admin-tools/htaccess-maker.html

I hope I can still count on you. ;-)

Best regards
Tim

Regarding .htaccess Maker, you will need to install the Pro version, .htaccess Maker is not included in the Core version. You have a Deluxe license, so you just need to download the Pro version from the website and install it twice back to back without uninstalling Admin Tools. Installing twice gets around an anomaly in the Joomla! installer.

Regarding the nitty-gritty, at first glance, that looks like a wild and crazy change, but keep in mind that you have SEF redirects turned off so maybe not. The raw Joomla! urls never were pretty, maybe we've just gotten used to the SEF ones. Does that url work for what you're trying to do?

At some point you have to transfer the whole site, then you can do a quick update with the database only. We were talking about the database transfer, which would not include .htaccess. I was a little off topic. :-)

Hi Dale

Thanks for your feedback.

I installed the Backup and Admin Tools Pro versions on the live web server. Then, I carried out a full site back up again and took that for restoring it on Localhost. The problem here was I noticed different php-Versions (webhost: PHP 5.3.28; localhost: PHP 5.3.13). Akeeba told me so. In particular, AdminTools have to be reconfigured. But how?

OK, I still have to read the documentation for that. But regarding different php-Versions do you have any valuable hints?

Following that it might not be necessary to regenerate the .htaccess file for the localhost.

Best regards
Tim

.htaccess files are still black magic to me. :-(

It is my understanding that when using .htaccess Maker, you have to regenerate the .htaccess file when you change servers because the url is used in the .htaccess file, it is hard coded in the commands. I confirmed that by looking at one of my .htaccess files. I can see the url used in one of the lines of the file. That url is entered at the bottom of the .htaccess Maker screen.

I am not aware of any reason that you would need to regenerate the .htaccess file because of a change in PHP version. Did you get that message from the installation script or from Admin Tools?

Hi Dale,

yes, I'll go for that.

>>Did you get that message from the installation script or from Admin Tools?

From the installation script. But I'll try first what you've told me.

>>.htaccess files are still black magic to me. :-(

Yes, one can read in the Akeeba UserGuide ...
... On the downside, learning how to tweak all those settings is akin to learning a foreign language.

That is pretty heavy load, I think ;-)

Have nice week-end

I'll let you know about the outcome.

Best regards

Tim

Hi Dale,
I've done what you told me to do.

My procedure:
I installed the Akeeba Pro versions (Akeeba Backup and AdminTools) first on my live site (Also, before backing up my live site I set all the SEO Settings to NO.), backed this site up (Full site backup), transferred the JPA-file to Localhost and unpacked it using Akeeba Kickstart. I of course configured everything according to the requirements for the Localhost. Atm the Akeeba Pro versions are installed twice back to back. Everything should run and work perfectly.
Then, I regenerated the .htaccess file on Localhost where I want to restore my site using .htaccess maker. The old file had been deleted beforehand. AdminTools automatically named the newly generated file ".htaccess.admintools".

The following things were also carried out:
I changed the php.ini file: from memory_limit = 8M to memory_limit = 64M
The LoadModule mod_rewrite line in httpd.conf is not commented out. There's no hash sign in front of it.
Before uploading db in Local phpMyAdmin I completely deleted the old db in Local.
I deleted Cache in the Firefox Browser and restarted all services of the WAMP-Server.
Furthermore, I tried to rename manually the .htaccess.admintools in favor of .htaccess. This was not possible, although it should be like that regarding the Akeeba documentation! However, renaming it to htaccess.txt was possible, but this did not have any positive effect at all. Having said that: Is there anything I have to change via my Windows Command Processor, too?
I renamed php.ini to php.ini.bak. This resulted in a Database connection error (Database connection error (1): The MySQL adapter 'mysqli' is not available), so I changed it back immediately.

I also used the Akeeba URL Redirection adding this missing "joomla" in the root. Please see the relevant attachment and other attached files. How can I make this happen? When I click on the Search button the URL leaves out this "joomla" in the root!

Please remember that I got this Akeeba message that different php-Versions (webhost: PHP 5.3.28; localhost: PHP 5.3.13) were installed. Can this be the reason for the existing problems? Unfortunately, there was no content in php_error.log available. This file is empty.

Any further support is much appreciated. My issue cannot be so difficult ;-)

Best regards
Tim

When you generated the .htaccess file, there was already one there, it was renamed to htaccess.admintools. That is a backup file. Your .htaccess file is a hidden file, you need to set your file browser to show hidden files in order to see it. That's why you couldn't rename htaccess.admintools to .htacess, because it already existed.

Let's edit your configuration.php file and change the line $live_site="" to $live_site="/joomla". You can't do that from within Joomla!, you can do it on your localhost with a file editor.

Tim, none of the problems are hard once we have them figured out. :-)

Hi Dale,
so far no success! :-(

Please remember that I still get this message on frontend:


Not Found

The requested URL /index.php was not found on this server.

Well, I've regenerated the .htaccess file (please have a look at the file Screenshot3.PNG). After clicking on "Save and create .htaccess", I get this Akeeba message:


JFile: :copy: Cannot find or read file: $C:\wamp\www\joomla\.htaccess

Does this information help you to find the solution? I wonder what I'm doing wrong.

Once you wrote:
>>You would need to change the site URL at the bottom of the .htaccess Maker screen.

Please have a look at the file Akeeba System configuration.PNG, if there's any mistake there.
I also edited my configuration.php file and changed the line $live_site="" to $live_site="/joomla". But this messed up my frontend alignment, please have a look at the file Screenshot2.PNG and backend, too, please see Screenshot1.PNG. I changed it back, but this remains the same!

Best regards
Tim

On the "not found" issue: if index.php is not found, how did you get the screenshot of your front end?

On JFile :copy: Is there actually a www folder in there? Does that folder exist on your drive?

You did the right thing on $live_site, when you see that "no css" look, $live_site is wrong. We may try again based on the answer to the question above.

Hi Dale,
I could clear things up at least to a certain state. The original state of frontend has been rebuilt by using .htaccess Maker. To make it work back again I had to delete the inserted "/joomla" in $live_site="/joomla" in configuration.php.

Attached I send you some screenshots in order to answer your questions.

>>On JFile :copy: Is there actually a www folder in there? Does that folder exist on your drive?

From Screenshot1.PNG to Screenshot3.PNG you can see the root wamp/www/joomla. So this www folder does exist on my drive. By the way, can you see any error when looking at these screenshots?

>> On the "not found" issue: if index.php is not found, how did you get the screenshot of your front end?

Please take a look at the other screenshots from Screenshot4.PNG to Screenshot6.PNG as well. When clicking on Site Preview I get the frontend and everything seems to be perfect. But clicking on the "Search" button which is Jomres related I get this Not Found: The requested URL /index.php was not found on this server. This is very unusual because on my live site an error like this does not appear!!! To my way of thinking there must be an error of the root settings. What do you think? Also, please take at look at the URL in frontend of those screenshots from Screenshot4.PNG to Screenshot6.PNG. I referred to this in one of my last mail.

The screenshot7.PNG is about the System configuration shown in .htaccess Maker of Admin Tools. Are the settings correct there?

Dale, have you ever encountered in your work anything like this before? The whole error stems from transferring my site from web to localhost. Help is still needed.

Thanks in advance.
Best regards and a great weekend
Tim

Tim,

I think I understand a little better now. If you simply type localhost/joomla in your browser, does your site front end load properly?

I am not familiar with JoomRes at all. Does it store any fixed paths in it's configuration files? That was a very common practice at one time, but most components have gotten away from it. We used to have to change those stored fixed paths when we moved the site.

Does JoomRes store the search results in index files, like the new search function in Joomla!?

Hi Dale,

thanks for your feedback. I'll try to answer your questions.

>>If you simply type localhost/joomla in your browser, does your site front end load properly?
Yes, it does.

I also tried to receive answers to this:

>>I am not familiar with JoomRes at all. Does it store any fixed paths in it's configuration files? That was a very common practice at one time, but most components have gotten away from it. We used to have to change those stored fixed paths when we moved the site. Does JoomRes store the search results in index files, like the new search function in Joomla!?

...by asking people in the Jomres Community Forum, but the issue remains so far unsolved. However, I'm in contact with a Jomres expert since this could be Jomres related.

How is it possible that the index.php file cannot be found on the wampserver, although the root wamp/www/joomla/index.php exists? Can there be anything wrong about the index.php file itself?

And still: I don't understand the fact that when clicking on "Search" the URL changes from localhost/joomla/index.php to localhost/index.php. Where is this joomla gone? And how can I insert it? On my live site this problem does not occur. Just to illustrate this better to you I'll send you the following 2 pix attached.

Thanks for your help.
Best regards
Tim

Tim,

I believe the issue is JoomRes related. It is not index.php that it can't find, it is something in that long string of parameters that is wrong. My guess is that JoomRes is remembering something from your live site that prevents it from running on your local site.

That is why I asked if /localhost/index.php would load the front end of your site. It is possible for a server to be configured incorrectly and "forget" how to handle an index.php file. That does not appear to be the case for your local server. The problem only happens with the JoomRes Search button.

I searched our support tickets, I didn't find a problem similar to yours. I did find a discussion between Nicholas and Vince from JoomRes where Vince stated that JoomRes does not use fixed paths. That was one of the things that could cause this and it appears to be eliminated.

Let's see if you get any answers from the JoomRes forum. If not, please let me know and we'll figure out where to look next.

Hi Dale,

yes, you are very right. I see the point. One has to realize that this issue is Jomres related, so contacting the Jomres community is indeed the more adequate solution.

Thanks so much for your precious help and kind emails. I’ll let you know about the outcome.

Best regards
Tim

Tim,

I don't know that it is a JoomRes problem, I don't want to accuse them of anything. What we know about what works and what doesn't suggests that they may be a better source of help than I am at this point. Let me know what you find out. Good luck!

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.