Joomla 3.4 installation issue - php

I am trying a Joomla 3 quickstart package. I uploaded all the files to the server and went through the 4 installation steps (Configuration,Database,FTP,Overview). I have selected "Default English" for language and I installed the sample data. After clicking the Install button Joomla creates the tables in db, and then stops and goes back to the Overview section without creating the configuration.php file and without creating some tables.
I don't know what I'm doing wrong. Anyone can help me to solve this?

You are likely running into a file permission issue. Check to see whether Apache can write files to your filesystem. Also check that you have enough space on your server.
A final thing to consider is to check whether you have some PHP configuration issues (such as session issues).

Related

Unable to run TYPO3 website to localhost

Currently I will upload a website to a server, but before I upload it I want to run this website on my localhost (I'm using XAMPP).
They gave me an archive containing the website files, based on the structure of the webfiles I realize TYPO3 is used.
Since I never tried using TYPO3, I tried installing it I followed this steps:
here
After the installation I run the sample, so far I don't have a problem running it on my web browser.
But when I tried to run the website that I need to upload
I'm getting an error.
here are the files inside the archive.
Here is after I extract it. As you can see I wasn't able to extract typo3_src which is the target location of index.php, t3lib and typo3 file that are all both in .symlink type.
And also the typo3 is not in folder type unlike the sample I run.
I'm not sure if the archive is broken/corrupted or I need something to do first before it will work. Can someone please help me regarding this issue?
You do not need to deal with those unix symlinks at all.
Just figure out or ask the person who provided you with that system, which version of TYPO3 you need to use.
Then go to https://sourceforge.net/projects/typo3/files/TYPO3%20Source%20and%20Dummy/ and download the appropriate zip package.
Decompress the package, delete all symlinks (typo3, t3lib, index.php) and just copy the corresponding resources from the package.
You then need to deal with the database and database connection settings in typo3conf/localconf.php or typo3conf/LocalConfiguration.php.
If it all works, you can then upload it like this to the server without using any symlinks.

Running Wordpress repo locally through MAMP. Assets not being pulled in

Currently I am trying to run a Wordpress repo locally for development. I am not using MAMP pro even though I still have a 9 day trail. I figured since I'm going to be using the free version for now I might as well work with that. I have my Apache & MySQL server running along with the Document Root pointing to my Sites folder where my projectName repo sits. I'm still running off of the default port of Apache 8888.
After I start the servers, I open WebStart and import my DB into phpMyAdmin. Everything works perfectly fine and the copy of my db gets imported. I then make sure that my wp-config.php file has the appropriate settings to access this db. I then click on My Website. This pulls up the content of the website. However, it does not pull in any of the assets(imgs/js/css). I receive the following errors in the console:
Failed to load resource: net::ERR_EMPTY_RESPONSE http://projectName.dev/wp-content/uploads/2016/09/logo-footer-1.png
Failed to load resource: net::ERR_EMPTY_RESPONSE http://projectName.dev/wp-content/themes/projectName/images/circle.png
And so the list goes on and on for pretty much every asset the project could possibly have. Now configuration is NOT my strong suit, and at this point I am at a loss of what could possibly be happening. Awhile ago I did follow a tutorial on how to setup my files so that I can access them in the web browser by simply typing the name of the project with the domain .dev, example: projectName.dev. I started having issues with this after upgrading to OS Sierra and it no longer works. Could this possibly be the reason as to why it is looking for these assets in the projectName at the .dev domain?
I apologize if this does not make sense. I am willing to provide anyone with any information on this as I need as much help as possible because I still need to level up my configuration skills. Let me know if you have questions.
The images and other assets are referenced with an absolute filepath (i.e. the URL of the server on which you first set it up). This has to be changed in all database entries. There are tutorials for this on the net, but the most simple version is to open the sql file in an editor and search & replace the general URL part in the complete database.
Be sure to keep a backup of the file - that might not work on the first try...

Multiple faults on Joomla installation

I have previously installed several different Joomla installation at the same hosting company without any major faults that couldn't be corrected quickly. Though I must say that I now find myself lost and don't know where to turn.. So here I am.
I have mulitple issues that I believe is all connected somehow.
Can't upload Images using the Media Uploader (Image size too large) though everything is set up correctly (max_file_size etc.) in PHP configurations and Joomla config.
Can't upload any other files in the Extension Manager either, since it says my PHP temp folder is not set. Though it is set, and writeble, have permissions etc. Also more than triplechecked the path, by FTP upload PHP-files to write out and verify the absolute path.
When I save something in the Global Configuration, it says my "Configuration.php" file is not writable. Permission is set to 777 even! If I go back and check, my settings is saved though it just said it couldn't save to the file?
Even tried to change to FTP-upload to see if I could bypass the fault somehow, tried both by setting it in Global Settings and by downloading the config file, change it manually and then re-upload it via FTP. No luck there either, seemed to just ignore my settings..
Updating Joomla seems to go just fine though, just updated to 3.4.1 to see if it made any difference but no. Running on PHP 5.6 right now though my hostingcompany just said they will downgrade to 5.4 to see if can make something change.
Otherwise, the website is fully functional! You can browse as usual, and write blogs etc. Though, not upload anything. Saving other settings work fine though. Should also mention that the website worked locally 100% before uploaded to the current server.
Any ideas where to start looking? Been Googling for the last 8 hours!
My webhost downgraded my PHP service to 5.4 instead, which solved all problems. Weird.

Joomla Upgrade 1.5.15 to 1.5.23

I am trying to upgrade joomla 1.5.15 to 1.5.23
I have downloaded the Joomla_1.5.15_to_1.5.23-Stable-Patch_Package from the joomlacode.org.
While trying to install this package from my administrator, the error will be displayed "Error! Could not find an XML setup file in the package.".
Or
Shall I extract this zip file and upload the files to server directly through FTP?
Please advise me..
Any help appreciated.
I would recommend a 3-step process personally to ensure the best possible outcome.
First - backup your site (I LOVE Akeeba Backups 1-touch backup solution); download the backed up site and install on a local host or development server.
Second, do your upgrade there (extract the files from the .zip and put them in the localhost/dev server installation).
Make sure that the upgrade didn't break anything, that everything still works appropriately and as expected and create a backup of the localhost/dev server site.
At that point you know the upgrade won't break anything.
Third, upload the unzipped files from version 1.5.23 via FTP into your root joomla directory (complete the upgrade as listed HERE.
Doing these steps will ensure the best possible outcome and will show absolutely ZERO disruptions on your live site in the event something you're currently using doesn't like the jump from .15 to .23 - which is a large jump and a lot of things are different (including which version of mootools is included!) So take caution and TEST FIRST!
I would advice you to do this::
Assuming you have access to all the files of website.
1.Now download directly 1.5.23 or 1.5.26 version(last update patch of this series.)
2.Extract the files and open them,you will notice them you need to only replace 4-5 files in that patch.
3.Copy each file and replace them with the current files in the existing websites.
Hope this helps.

A question about duplicating Drupal installation on another server

I have hired a programmer overseas to develop a Drupal website for me and he has done a very good job (the site is installed at his server). I payed him and he sent me the Drupal files and the database .sql file.
Here is what I have done so far:
1- I have created a database on my server named something different from the database file he has sent me and imported the .sql file with no problem. (naming the database as the one he has used during development is not possible for me)
2- I have uploaded the Drupal files to the root of my domain.
3- I have modified drupal/site/default/settings.php and put my database information there and I have modified the $base_url variable there.
The problem is that when I access the website I get a white screen and nothing else (even when I click on show source on my browser, it is empty).
I tried to do the same on a localhost on both Mac and Windows using MAMP and WAMP respectively, and I got the same result (empty screen)
anybody has any suggestion about what seems to be the problem?
Best Regards,
Its a PHP WSOD error most likely. Do you have a way to check crash logs?
Have you looked at The White Screen of Death? Typically when faced with this issue and unable to quickly find the cause I return to this handbook page to go through the possible causes. Unfortunately this is a common symptom of many different problems and can be difficult to pin down.
if anybody has the same issue. Problem has been solved by adding the following line to the PHP settings.php file:
ini_set('memory_limit', '64M');
Thank you all for the help.

Categories