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.
Related
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
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.
When I make a change to “app/design/adminhtml/default/default/template/page/head.phtml” or other files in the adminhtml folders, the changes I make have no effect on the site. The site seems to be using old versions of my files but I have no idea where it is getting them from. I have deleted the cache multiple times and logged in/out of admin. I’ve also managed to turn on path hints in the admin panel and can see that the correct files are being used but the code in the files is incorrect. If I rename the file to _head.phtml then as you'd expect, the styling, js and meta tags etc go missing but when I make a simple edit to that same file the change is not reflected.
I recently upgraded from 1.6.2 to 1.7 - Am I missing something?
I'm not a wordpress person - but I had to move Wordpress to a subdirectory from root for a person the other day.
I followed the steps on the Wordpress site - and everything transferred fine. All the articles, logins, etc. display fine.
The issue is the images in the articles - they are linking to the old address (from root: www.domain.com/link/to/image); the images are now in a subdirectory (www.domain.com/blog/link/to/image)
What is the best way to resolve that? Obviously going into each article and re-linking would solve the issue but is there an easier, less time-intensive way? .htaccess? some other bit of coding that would be helpful? Again, I'm not a wordpress guy so I'm not sure what would be the best way to do this but I would think there has to be something besides manually going through blog posts?
Have you tried going to:
Settings in WP-Admin >> Media Settings
Then try changing both:
"Store uploads in this folder" Default is wp-content/uploads
"Full URL path to files" Configuring this is optional. By default, it should be blank.
This should do the trick
Search RegEx is a good plugin to be able to search and replace with Grep through all posts and pages.
i want to change default template in phpbb3. for this where i have to made changes. i am trying to changes file inside style/subsilver2/template...but i didn't made any right .please help me ..in which file i have to made changes.i have also try in admin section in style..but not successes... if any one have clue..please help me.
Thanks
Manish
It depends what part of the page you would like to change, since the template is a set of many HTML files with preprocessing instructions. They are located in:
[PHPBB_Folder]/styles/[Theme_Name]/template
You can find the right html file by searching for a specific part of source code copied from the live page of the forum.
Important note: when you're changing phpBB template files, don't forget to reset the template cache in the forum admin panel (go to Admin / Styles tab - and clear cache for what you changed, Template, Theme, or Imageset.
I hope this helps.