I have try to change default welcome message in magento 1.9.1.after some analysis i found that i need to change it in header in system->configuration->design tab.But am unable to find the header tab in magento 1.9.1
You are missing a step..
System > Configuration > GENERAL > Design
There are two ways to solve this issue.
First is to install new fresh magento which takes long process.
OR
Copy the core file system.xml in app/code/core/Mage/Page/etc
Create a similar directory folder in local folder (app/code/local/Mage/Page/etc)
Paste the system.xml on that directory
Clear your cache and refresh your page.
If the tab is still missing check your local folder and its file names. If there are no discrepancy, proceed to the first option.
I'm not sure if this is a bug of magento. It usually occurs during installation of magento upgrade.
You can refer to this links.
Missing HTML Head section from admin system->configuration->Design in magento
Magento html-head dropdown missing
Related
After upgrading the joomla site iam getting the following error and administrator page is blank.
Fatal error: Can't use function return value in write context in /home/cll/public_html/libraries/regularlabs/src/File.php on line 283
Please help me to solve this issue.
It's clear that the problem comes from a regularlabs extension so you should disable it.
Since your admin page is blank, you can do this via the file system. Log in to your FTP account (or use the control panel's file manager) and access your root folder (/home/cll/public_html/). The extension you are looking for is probably a plugin so you'll find it in the plugins folder. I assume you'll find the extension in the /plugins/system/ folder (full path: /home/cll/public_html/plugins/system/).
When you'll find the extension's folder look for the plugin's PHP file and rename it.
For example, if the problem comes from "components anywhere" plugin (it's a regularlabs extension) search for componentsanywhere.php and rename it to something else (eg foobar.php).
If this doesn't help contact the developer to help you, he is a good guy.
I updated my site from Magento 1.8.0 to 1.8.1 and now the checkout process won't proceed after choosing a shipping method. Can someone please advise on this matter?
Thanks
Solved. In the checkout.xml file of our template, we had to make the following change (change the methods.html file to info.html) The new base template could not override this line and therefore the checkout-payment-method-load div was not writtten. See here: https://magento.stackexchange.com/questions/10984/magneto-v1-8-one-page-checkout-not-loading-payment-information
I just copied the checkout.xml file from app/design/frontend/default/modern/layout/checkout.xml and overwrote the one in our custom directory app/design/frontend/YourName/default/layout with that one, and it fixed the problem. Same with the "white page" PayPal issue. If you have a paypal/ folder in the template folder of your custom skin you also need to replace that with the default one I guess for the paypal issue.
There is a strage problem in my website's magento connect feature. Whenever I will click on Magento Connect, it will show me the installation page of magento.
The url is something like this
http://www.mystore.com/downloader/?return=http%3A%2F%2Fwww.saletab.com%2Findex.php%2Fadmin_panel%2F
Is this because someone changed core file? Or because I am ruining magento 1.7 and 1.8 is released?
Please note that another instance, of the EXACT same code and database works fine when I click on magento connect, but not this one.
Please tell me how to resolve this problem?
first you need to check your file directory , there is 1 folder " downloader " if this folder is rename then please set name that i mention in quote , and if not available then please download fresh magento and copy that folder to in your file directory.
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.
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.