I have created a new theme for magento.I want to submit it to the communtity.When i tried to package extension,I m getting The package data has been saved message,but there is no package in var/pear directory.Is it not possible to pack extension in localhost?Do you need more information?Any help would be appreciated.
Please see this article:- Magento: How to create extension package? (IMAGES)
Check if the data is filled correctly.
While creating your extension package, under Package Info -> Supported releases
If you have chosen "1.5.0.0 & later" then your extension package is stored in var/connect directory. This supports Magento connect 2.0.
If you have chosen "Pre-1.5.0.0" then your extension package is stored in var/pear directory. This is for Magento connect 1.0.
If you have selected both options, then the extension packages is stored in both places (var/connect and var/pear).
When uploading the 1.0 version from var/pear – Magento Connect will
make the 2.0 version for you. If you wish to only support 1.5 and
higher versions of Magento only then only upload the 2.0 file from the
var/connect directory to Magento. Source:
http://www.magentocommerce.com/wiki/7_-_magento_connect/packaging_a_magento_extension_in_1.5
Edit:
I tried to create a package with app/design and skin folder. It worked fine and I could see other folder and files in the package file inside var/pear.
I tested with default theme and default skin. In 'Contents' section, I kept like this:-
Target: Magento Theme Skin
Path: frontend/default/default
Type: Recursive Dir
Target: Magento User Interface
Path: frontend/default/default
Type: Recursive Dir
What version did you select for "Supported releases"? Check in the var/package/ folder too. Check both folders have user and group write access.
Packges are saved with a .tgz extension, so running
find . -name '*.tgz'
from the magento base folder is always a good way to find your packages.
Also, as of 1.5, Magento changed their package management system. This is why you had to choose a supported releases option. For 1.5 and later packages Magento will, by default, drop the files into
var/connect
The var/package folder is only used if you opt to create a pre 1.5 package.
Related
I have lost the installation zip file of one of the component that I installed in one site. How do i export it and repackage it so i can install it in another site?
Given that the component's manifest file is current, you can use the Extension Exporter that I wrote recently:
https://github.com/GreenCape/extension-export/releases
If you have installed additional languages, you can add them to the manifest file manually; they will then be included in the export automatically.
I created a custom module that represents a custom payment method, the steps I follow are;
1) Create a module architecture in /app/local/NameSpace/MyModule
2) Create an xml file in /etc/modules to configure my module
3) Create templates /design/frontend/base/default/template/mymodule
The module works well, but i want to reuse the module in other projects with all in one installation. now, i want to know if i must develop a script to copy the xml file in /etc/modules and templates manually? or there is an existing solution in magento 1.9 to do this operation?
Thanks in advance,
You want to create a Magento Connect package. There's a UI for doing this under the System Magento menu (although the UI is sort of terrible) and some googling around should set you right. Once you have a connect package, you can install it into any system via the /downloader UI (also available via the System menu) or the ./mage CLI command.
Also -- if you choose "Magento Other" as the role for all your files, your resulting tgz archive can simply get uncompressed/unarchived into any Magento system's root folder. Also of interest -- my script for creating Connect Packages from raw tar archives.
I am developing a magento extension. After getting help from stackoverflow, I am able to create a package extension which is stored in [magento]/var/connect folder. I noticed that package.xml, myextension.xml and myextension-1.0.0.0.1.tgz files are created therein.
I created another magento instance locally where I want to load that package and test. It's not possible to get my extension verified by magento team and then use it quickly or is it? I copied those package files under /var/connect of the test instance but I cannot see that appear in admin-> system -> magento connect -> package extensions.
Any idea how I can do that? All I need is he ability to let my customer have my zip files(package files), then they will upload somewhere. Any help would be appreciated.
You can upload packaged Magento extension by going to:
System > Magento Connect > Magento Connect Manager
then uploading the package under the Direct package file upload section.
Furthermore, if you decide not to package your extension, just copy the working file structure of your extension to it's own folder, and you can simply drop your extension files into the working root directory of compatibility Magento installs. Just be sure your extension file structures are correct. EX: app/code/local/MyNamespace/MyExtension etc.
I'm using Magento 1.6. I've created my own theme (mytheme) under base.
So my file structure is app/design/frontend/base/mytheme
I could also develop my theme under app/design/frontend/default/mytheme
Which is best practice? And what are the implications of using base/mytheme rather than default/mytheme?
Cheers,
Eddie
I do disagree with the solution of Mr Storm.
ref: http://www.magentocommerce.com/knowledge-base/entry/magentos-theme-hierarchy
Those documents recommend You avoid to use the package default (as the base package too)
You have to creating Your own package 'mytheme' and to define a theme 'default'
ref: http://info.magento.com/rs/magentocommerce/images/MagentoDesignGuide.pdf
"Please ignore legacy Magento instructions and tutorials that instruct
you to create your custom theme inside of the default design package,
or to edit files in the default/default directory directly.
Rather,
the method that affords the best upgrade path for your theme and the
most protection from accidental changes is to create a new designpackage
and to create your custom theme inside of there."
So the correct answer is
app/design/frontend/your-package/default
Do NOT use:
app/design/frondend/default/your-theme
You don't want to put your theme in the base folder. The base folder is meant to contain the "core" theme that ships with Magento. It's the ultimate fall back, and the last place a file is looked for. It was specifically introduced to provide a place where core Magento developers could blow the entire directory away and replace everything (if need be)
To create a theme for Magento, you'll want to create a theme folder in your design package
app/design/frontend/default/mytheme
Then, in the admin go to
System -> Configuration -> Design
and enter mytheme in the Default field. Your theme will now the the "default" place Magento looks for files. If it doesn't find one, it will fall back on what it finds in the base folder.
How do I install the Magento Bitcoin currency extension on a Linux box with standard LAMP stack?
I have already searched, read the documentation, and put the files in the root Magento directory (just as the instructions say to do: https://github.com/ticean/magento-bitcoin/wiki/Installation).
Copy files from /lib/ into your /lib/.
Then everything in /app/ into your /app/.
Make sure to upload /design/ into the correct template you are using.
Code is going into /community/, NOT core or local.
Finally, ScaleWorks_Bitcoin.xml goes into /app/etc/modules.
Verify that Magento can see the module in Admin -> Config -> Advanced. Does the module show up on that list?