I just installed Magento 1.4.1.1 on my Ubuntu Apache server and everything is working just fine aside from one thing:
The Magento Connect Manager simply brings up a blank page. In Firebug it is just <html><body></body></html>. I read that it might be permissions but I gave 777 permissions to the Magento directory and all subdirectories and still the blank page.
Any ideas?
Alright, for some reason it was looking for a PEAR file in a non-existant location. Magento included this in line 27 of PEAR.php:
$_pearDir = dirname(dirname(dirname(__FILE__))) . DS . 'downloader' . DS . 'pearlib';
However, this led it to a directory that included "/includes", which wasn't correct. I ended up just putting
$_pearDir = dirname(dirname(dirname(__FILE__))) . DS . '../downloader' . DS . 'pearlib';
Notice the only difference is the "../" in front of downloader to remove the "/includes" directory from the path. But my real question would be why Magento would have this error in the first place. This couldn't have happened to everyone who installed Magento on an Ubuntu server, right?
I got the same error today without changing anything (no updates etc.) ... blank page when trying to access Magento Connect from backend.
With the help of the answer above I was able to get it to work again. So in Magento base directory go to /includes/src/Varien/ and make the change in Pear.php (include ../ before download) in line 12.
It still would be nice to know what really caused this problem.
Not sure if my solution is 100% related to your issue - but I had been struggling with a blank page for Magento Connect Manager too (version 1.4.0.1)
After a couple hours I discovered that the pear.ini file (/downloader/pearlib/pear.ini) needed to be updated.
It may happen that the filepath references in your pear.ini are not up to date in the case that you changed servers, installations or Magento directory locations.
Therefore you need to do two things:
Open your pear.ini in a text editor and update all filepath references with your current Magento directory location.
Adjust the number of characters for each string. A bit of a pain, I know but it works. (you can use a word editor to do your character counts)
For example:
s:59:"/var/www/vhosts/mysite.com/httpdocs/Test/downloader/pearlib";
where "s:59" is the number of characters in the path /var/www/vhosts/mysite.com/httpdocs/Test/downloader/pearlib and "Test" is the old directory.
Upon going live (i.e removing "Test" folder) This needed to be updated to:
s:54:`/var/www/vhosts/mysite.com/httpdocs/downloader/pearlib`;
Let me know if you have luck?
Related
I have this odd situation. When creating (or updating) a product in the images section whenever I select a file (or multiple files) the list the selected files doesn't appear therefore I can't upload any images to a product. I don't have ANY errors in the console or in the log and the most odd is that when running the code on a localhost it works. All the required folders on the server exists and they are writable. Any ideas on what could be the reason?
Please check Flash browser plugin working. It's should be installed and enabled.
ok, guys, I found the problem. It easy at it seems took me a lot of time to realize that it's only working when accessing the website with www
I have installed an extension , On installing it magento shows its progress in terminal properly ...
But in actually it is not installed .
Neither the extension list includes its name.
For every extension the same problem exists .
please suggest me what may have gone wrong .
You have cleaned cache from system->cache management right? Also some extensions require you to logout and login in backend otherwise they give you 404 page.
Also try to look in system->configuration->advanced->disable module output. You can see all installed extension on your installation.
Edit: also try to see in app/etc/modules if there is an xml with extension's name, and if in app/code/local or app/code/community there is a folder with all files. If there are not any, maybe it's a problem with permissions.
Try to see section "Permissions not correct/insufficient" in http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/installing_magento_via_shell_ssh
I've successfully installed Fishpig's Magento WordPress Integration extension. I followed the instructions where you install via Magento Connect and had no problems. This is by the way all on the development server which does not have Caching or Compiling enabled.
The Magento cart is installed in the webroot directory and WordPress is in subdirectory "wp" as stated in Fishpig's instructions. The Full Integration blog path is /blog.
PROBLEM:
When I visit the blog's page it is not using the Magento theme. I even set it to use the same layout (same as CMS's homepage) We have a custom Magento theme. Maybe there is something we are doing incorrectly Magento theme wise for Fishpig's extension not to work. Screenshots to come eventually but the host (DataGram) is down due to the flooding Downtown. Should be back hopefully today.
To clarify... WordPress is using its own database. In the Shop's admin panel->WordPress tab I setup Full Integration and set the path to "wp" and the blog path is blog.
So, now if I visit for example... example.com you are in the shop and if you visit example.com/blog you are in the fully integrated blog.
Bottom line is it seems to be configured fine in the admin panel. I am not requesting the blog page from the wp directory (I.E: example.com/wp) but from the fully integrated page (example.com/blog).
Our problem could be similar to what this person is experiencing:
Magento - FishPig Integration - Not getting correct template for /blog
Have a great weekend all!
Best Regards,
George
Huzzah looks like I got things working :-)
The culprit was that this file:
"app/design/frontend/default/eboost/layout/wordpress.xml"
^^ was pointing to the wrong template filename. Corrected and was good to go. Modified line was number 66.
Funny thing is that on the top of that XML file it states:
"
Option 1 - local.xml (recommended)
Create a file named local.xml in your custom theme's layout folder. You can then make changes to the layout there by
using the relevant layout handle. This allows you to leave this file intact and recieve new features
when upgrading the extension.
Option 2 - copy this file
Copy this file and it's contents to a new file in your custom theme's layout folder named wordpress.xml.
Each time you upgrade, you will need to check with your copy of the file and
the copy in app/design/frontend/base/default/layout/wordpress.xml for changes and merge any you find"
Now, as stated in my Original Posting I installed FishPig extension using their instructions: http://fishpig.co.uk/wordpress-integration/docs/installation-and-configuration.html
^^ Therefore I don't know why it is setup using Option 2. That wordpress.xml is in our theme's layout directory.
.
.
.
I feel I should also state the other changes I did even though it doesn't seem like it contributed to making it work. Just doing for completeness:
-- Renamed the subdirectory /wp to /wordpress and changed all references to dev.eboost.com/wp to dev.eboost.com/wordpress within the DataBase using http://interconnectit.com/124/search-and-replace-for-wordpress-databases/
-- Removed .htaccess from /wordpress folder
So bottom line is looks like it is working normally. We are now set for working on redesign for site.
--George
Have a look at this.
http://www.wellicious.com/gbren/wellblog
I also used Fishpig and it is working.
What do you mean by visiting the blog page? Do you request the blog page from the wordpress directory?
If so, it doesn't change its design.
You have to request the blog within your shop.
This is my first time working with Magento and here is what happend: I spent two days reading the documentation and tweaking the settings to fit my needs. I then installed this theme:
http://themeforest.net/item/decostore-magento-theme/1876494?WT.ac=category_thumb&WT.seg_1=category_thumb&WT.z_author=8theme
The problem is that the theme didn't work the way I was expecting and now I'd like to rollback to the default theme and completely remove everything added by this theme to my installation.
Unfortunately, I didn't backup the installation and database before I installed the new theme and I have no idea where to start.
Thanks in advance.
1. Switching back to default theme
Go to the admin area and then system > configuration > design
Change "Current Package Name" to 'default' and make sure all inputs under the "Themes" section are empty. This will return you to the default theme.
2. Completely remove everything added by this theme
I take it from your question that you are not using any form of source control. Might be an idea to look into this for the future :)
Magento 1.7 has introduced backup and rollback features so you may also want to check that out.
If this is the case, backup everything before you start removing files and directories as described below
Anyway, to completely remove all files and directories added when you installed the module, unfortunately it will simply be a case of manually finding the files and directories deleting.
The easiest way to do this will be to find the original source code you received when you purchased the theme and removing the corresponding files from your site. When removing directories be careful to only remove those specific to the theme - It will have been sent to you structured so that you can easily drag straight in to your web root - so will contain some other directories required by Magento, simply to give it the correct hierarchy.
At the very least there will be files and folders specific to the theme located in the following directories:
app/design/frontend
skin/frontend
js
and also most likely some more in the following:
app/etc/modules
app/design/adminhtml
app/locale
I know the result for this can be different for everyone, but in case someone else comes across my specific case, it was the N98 folder under app/code/community/N98 that caused the problem. Particularly their CustomerGroupCheckout plugin as shown here: https://github.com/amenk/N98_CustomerGroupCheckout
Removing the N98 folder brought back the configuration page.
I have a rather simple question.
I want to install a new magento theme. In the documentation it says to overwrite the default 'app' and 'skin' folders with the theme's 'app' and 'skin' folders.
"8. Upload the "app" and "skin" folders from the template themeXX folder to your Magento root
folder (accept the replacement)"
However, when I am doing that, it prompts me to download magento again thru the magento installation wizard.
To me, it sounds more reasonable to just copy the contents of the 'app' and 'skin' folders of the new theme into the default 'app' and 'skin' folders of the magento framework as they contain some other folders that probably should remain intact.
Any suggestions please?
Did you first install the default Magento in the folder where you want to run it? You will need a running installation of Magento before you can go ahead and install a team.
If it keeps promting you check that you're on the right address in the address bar of your browser. To install magento you would have been redirected to [magento]/downloader/
As a last resort you could open up index.php and remove the code redirecting you the downloader folder, but at this point you might be better off re-installing Magento (remove everything in the directory and follow the install steps again) since something probably went wrong.
After you've installed Magento check if you see the default store interface and can access the admin areas before installing anything else (including a theme)!
There's absolutely no need to overwrite the app and skin folders. In fact, if you do so, you could easily overwrite just about all of Magento's functionality and break your system.
That would be why you're getting a new installation prompt.
What's the theme you are installing, and what's the link to the page where they give that information?
Generally a theme will be packaged will a folder structure that looks like this:
theme_package
theme_package/app
theme_package/app/code
theme_package/app/code/local
theme_package/app/code/local/Namespace
theme_package/app/code/local/Namespace/Themename
theme_package/app/code/local/Namespace/Themename/Block
theme_package/app/code/local/Namespace/Themename/etc
theme_package/app/design
theme_package/app/design/frontend
theme_package/app/design/frontend/base
theme_package/app/design/frontend/base/themename
theme_package/app/design/frontend/base/themename/layout
theme_package/app/design/frontend/base/themename/template
theme_package/skin
theme_package/skin/css
theme_package/skin/js
and so on.
This content needs to be merged as you said.
Many of these folders already exist, for instance app/code/, app/design/frontend/base/, skin/css/, skin/js/
Just copy any new files or folders.
#george i know it's been a while since anything has been said on here, but i just want people to know for future reference that you only have to add to the app/design/frontend/default/[theme name] and skin/frontend/default/[theme name] folders like sg3s stated. i lost about 4 hours to this tonight b/c i bought a theme and they didn't specify that you only need to add to the folders not overwrite them.