I updated a Joomla website for a customer of mine. I did this in XAMPP. Now, when transferring it to the server, I have some problems. I can't install extensions anymore and I get the message:
JFolder::create: Infinite loop detected
Warning: Failed to move file!
After some reading I found out it's possibly caused by the log and tmp folder, but I don't know how to rename them to work. (The link to them in the config.php file)
public_html > tmp / log (both tmp and log are in the main directory of public_html)
How would I set them up to work? And is it definitely this that is causing this error?
You can actually edit those values using Joomla's back-end. Go to global configuration settings menu option, one of the text fields is in the Server tab and the other is in the System tab. If you can, put the full directory path of the server in for the values.
Related
I've moved a legacy site on Wordpress 3.8 from one server to another. The new server is on PHP 7 and I continue to get the error below:
Your PHP installation appears to be missing the MySQL extension which is required by WordPress.
I've tried installing the Wordpress command line tool WP-CLI but still get the same error.
What should I try next?
You are going to need to do a manual update.
Download the current/or version you need and once you’ve downloaded it, extract the zip file to your computer. Then, open the folder that contains all of the WordPress files and delete the following items:
The wp-config-sample.php file.
The wp-config.php file (you might not see this file – just make sure to delete it if it’s there).
The wp-content folder.
Once you’ve deleted those items, upload the remaining files/folders to your server via FTP. When prompted about duplicate files by your FTP client, tell it to overwrite all files:
Downloaded the latest phpMyAdmin to be used on macOS 10.15 Catalina (local webserver), extracted the phpMyAdmin files to my web root.
During the setup I chose config authentication and now when I visit the setup page I'm getting some mysqli error.
I deleted the entire phpMyAdmin/ dir and wanted to start all over again. However to my surprise, the previously entered (incorrect) server details are still there.
I would assume the any config.inc.php would be saved within phpMyAdmin's own dir, but apparently it's saving this data somewhere else.
How/where can I find it, so I can delete it and truly start a complete new phpMyAdmin setup from scratch?
P.S. I already tried:
/etc/phpmyadmin/
/usr/local/phpmyadmin/
/usr/local/etc/phpmyadmin/
/usr/local/opt/phpmyadmin/
But neither of these dirs exist.
If you've simply downloaded the phpMyAdmin file yourself and uncompressed it to your web root, then the config.inc.php file goes in that phpMyAdmin folder. If you've used brew or some other package manager, they each have their own location for configuration files, but that doesn't seem to be the case here.
It's not clear why the old server details have been retained, maybe your browser has cached the old page or something, but the only place that phpMyAdmin looks for the configuration is in the main folder. Is there a chance you're seeing the defaults, rather than some custom setting? (The defaults would be to use auth_type cookie connecting to host 'localhost').
What is the specific mysqli error message you're seeing?
I've read a lot on the internet about how to move Joomla. So, confident in myself, I've moved this old joomla 1.5 website to another machine.
I've copied files and database (data and user) as it were in the old machine on the new. Same folder name, same apache2 configuration, same .htaccess, same database configuration, name and data, same operative system, same php version...
Unfortunately, any page I'm trying to visit return a "404 component not found error" like it cannot find the page.
I cannot get what is happening. Mooving Joomla requires particular attentions, after copying files and database?
You have to change in configuration.php file the path of log and tmp directory, It's hard for you to have the same path in a different machine.
In the log file there are more details? Type what component.
Some things to check when a moved Joomla website is not working as expected:
the .htaccess file (in particular, check the RewriteBase /, Options +FollowSymLinks lines or any non-standard lines - compare with htaccess.txt for the default settings)
the configuration.php file, check tmp and logs paths are correct, try setting $live_site = ''; if it's not already
check for any php.ini files in the root folder and also in the /administrator folder - php.ini files are often not needed any more as you can configure PHP settings via cPanel or similar
try disabling URL Rewriting in Global Configuration
We have moved out magento site to another host. But it is redirecting to the old site
We did following changes before moving the site
1. DB backup
2. files are zipped and copied to another host.
after moving the site to another host
1. changed the /web/secure and /web/unsecure values in the DB.
2. In magento files /app/etc/local.xml changed the database name.
3. cleared the var/cache
4. cleared the var/tmp
5. cleared the var/session.
but still the magento site is redirected to old site.
Can any one help me with this.
Thanks
Several steps involved in cloning or moving a website.
NOTE: It's common practice to empty the var/cache, var/session directories before copying to new location. Clearing cache is mentioned below as it's necessary to clear the cached config after you've run through the list and properly set database access, BaseURL, etc.
Copy application files to new location and import database into MySQL. (best to do this with a tarball and database dump sql file, ftp has issues with things like getting .htaccess files to transfer, case to matter, etc.) Note: more sophisticated Magento admins use rsync, it's far easier.
(important!!) Make sure file/folder permissions and owner/group are correct so that var/ folder system is writable. Otherwise the Magento cache gets written in system /tmp instead of Magento var/ and only a server reboot or manual deletion will clear Magento cache out of /tmp . Also, not having var/ writable means that any drastic errors that write a file to var/report/ will fail to write any stack traces, compounding your installation heartburn.
Make sure app/etc/local.xml points to the proper database and make sure if you back up the original local.xml that it doesn't end in .xml -> needs to be something like local.xml.sv1
Change your database entries Unsecure BaseUrl for and Secure BaseURL to point to your new location (http://www.example.com and if ssl cert installed https://www.example.com respectively). Use phpmyadmin to look for the paths web/unsecure/base_url and web/secure/base_url in the core_config_data table. (Note: entries will exist for each scope set, minimum is Global)
Manually clear your cache by deleting all the mage--? subfolders in var/cache
If you were using the compiler on the previous site, disable compiler with SSH command line php shell/compiler.php disable from the Magento root.
Attempt to load your admin backend, you should be on the new server URL now.
Following these steps should clear all the hiccups that cause Magento to adamantly redirect back to the old server. And believe me, I've had them all happen.
I have made a copy of and edited the wp-config-sample.php file with all of the database details that should be in it (obtained from my host, and also created in mamp pro data user).
I have also replaced the unique phrases and corrected all $ with S as suggested by WordPress forum, forums here and tutorials.
I also then saved it as wp-config.php as suggested. When I then go to Wordpress and say submit it says that the file already exists.
In my Wordpress folder there is both the original sample file and the edited one I was asked to either create or edit. If I delete the sample page and submit it says I am missing a wp-config.php and need to create it. I put it back and it says the file already exists. I then edited the wp-config-sample.php file and just corrected the name as wp-config.php and still nothing I try or change works.
(I solved this problem as my root password in mamp pro was not the same as in the wp.config file, as soon as I had that corrected it all fell into place and worked :-))
sorry, i am not allowed to comment, but are you developing on a local machine or through a web hosting? I believe your in Mac. The safe bet here would be, for you, to delete the wordpress folder in the htdocs directory, untar it again there, and from the browser go to localhost/wordpress-folder-name and follow the wizard. (open up localhost/phpmyadmin to setup MySQL database)
If you want to put the wordpress in a live web host, then use ftp to upload the wordpress directory (you will have to change the settings). So, actually, unzipping a fresh copy of wordpress directly, and following the wordpress setup wizard online would be easy. For the MySQL database, use the settings provided by the host.
In these steps, you never have to touch the wp-config-sample.php nor wp-config.php file.