It's really weird what i am really dealing with here, in all the books that i read about learning and developing themes for Magento it points out to the directroy app/design/frontend/base/default/ and that it should contain three folders (etc. layout, template)**but when i go and search for it i only come up with **app/design/frontend/Magento and the Magento folder is empty,reinstalled Magento many times so i am sure it's a clearn installation, what is going on here, why i can't see those directories?
app/design/frontend/base/default , this path restricted to before and till magento version 1.9.x. You shall be downloading and using magento 2.0. For this you have to download magento version 1.9.x
Related
There's two directories in the Github respositories:
magmi
magmi-0.8
Which one should I use?
I had this question as well. After sniffing around, it looks like the magmi-0.8 folder may be reserved for the future releases of Magmi 0.8. The current stable is 0.7.19
I tried to run the magmi-0.8 version but got a bunch of errors, so I am now running the app from the base magmi folder. Fingers crossed this version plays nicely with Magento CE 1.8
This post provides more info:
https://github.com/dweeves/magmi-git/issues/12
This is not something standard for GitHub.
You're rather referring to Magento Mass Importer project hosted on GitHub.
As you're starting now, you should use the magmi directory, as it has the most updated code.
I'm using phpBB3 for my forums and have installed the Ultimate points mod. Its working perfectly on the backend, tacking users points ect, but it is not publicly displaying them.
www.rise-co.com/phpBB3
I have followed these instructions
http://www.rise-co.com/UltimatePoints/install.xml
But keep getting a parse error, like its not defined properly.
What version do you have installed? All the version up to 1.1.2 have issues and will not install properly via AutoMod. A developer ported this mod into a great style plus updated it to work with phpBB 3.0.12.
This is the link for the MOD download updated: http://www.sitesplat.com/phpBB3/viewtopic.php?f=7&p=3813#p3813
But you need to be part of the members who bought FLATBOOTS style to have access to it, amazing style by the way. This is the style link just in case: http://themeforest.net/item/flatboots-phpbb3-/8536771?ref=ThemeSplat
How i convert my current website of joomla1.5 to joomla2.5
please anyone help me
When i using jUploader it is only allow to convert joomla1.5.18 to 1.7 but i need joomla2.5
Thre is a lot of documentation out there on how to convert Joomla 1.5 sites to Joomla 2.5.
You need to use an extension such as JUpgrade to upgrade your site to 2.5.
Please bare in mine that this will update your database tables and core extensions such as com_content, mod_login etc. This will not upgrade 3rd party extensions that you have found from the Joomla Extensions Directory. You will need to go back to whereever you downloaded these extensions from and see if there is a Joomla 2.5 compatible version of them, and install them, else you'll need to look for an alternative.
Seeing as you have waited all the way till now, you might be best off upgrading again to Joomla 3.x. Even though this it eh short term release, it is the way forward, will save what could be another time consuming upgrade in the future.
Oh and as always recommended, please make sure you take a backup of your site before the upgrade.
Hope this helps
I know there exists tools that migrates Joomla to Wordpress at database level. But my problem is I don't have access to Joomla database anymore. I only have whole Joomla! 1.0.x site's local copy which was taken 2 years ago. Is it possible to migrate that posts to my Wordpress site?
Or should I copy-paste all content to a CSV file and use an Excel importer ?
Not specifically for Joomla , but I have made such a thing in the past several times while migrating from some Custom Cms's
It will depend on HOW BIG is your site and how much information you need to migrate (and it's complexity) but you can always go for HTML SCRAPPING / PARSING.
As from this point , GIYBF . And your Coding skills.
One of the best one IMHO is Simple HTML DOM ,and another that many recommend but I personally never used are htmlSQL And phpquery .
But there are also a lot of Tutorials on google ( here also and EXAMPLE TUT) explaining how to do it , and also a lot of questions here on SE and a list of options (not PHP exclusive).
The other option (which is basically the same , but without libraries) , is going or REGEX , like in this very simple example..
If you don't have the DB, then you don't have the content. All of the content on a Joomla site is stored in the DB. If you only have the Joomla files, there is nothing to copy and paste in to a CSV.
Try using this script. http://azeemkhan.info/2008/joomla2wordpress-import-wizard-v3/ Note you will need to install an old version of wordpress first and THEN upgrade your wordpress version.
There's a useful guide on this here and info on utf-8 support here.
Hope this helps
I created a theme on my own magento website, and uploaded it to another magento website, but when i go to the frontend of that website i get this
Fatal error: Class \\’Mage_Core_Helper_Cookie\\’ not found in /home/winterwa/public_html/app/Mage.php on line 516
I searched for a solution and tried this one described in this topic:
http://www.magentocommerce.com/boards/viewthread/280318/#t401019
(cookie.php in app/code/core/mage/core/helper) but it didn\\’t help a thing.
Any suggestions/solutions for this??
It sounds like the two different Magento installs are running different versions of Magento. The file in question is only added to Magento in version 1.7. I can only assume that you have taken a fresh install of 1.7 and based your theme off of the default / base theme for this. Therefore when the theme gets added to an older version of Magento it is trying to load Blocks / Templates that you haven't overloaded and that just don't exist in the base template.
Unfortunately this won't be the easiest thing to fix. You will need to go through the layout/template files, removing references that add blocks or use helpers that don't exist for the current version of magento. For the issue you mention, you should be able to find by searching for helper('cookie') in your template files.