I have tried installing many free and paid plugins but every time I am getting this error
CONNECT ERROR: Package file is invalid
Invalid package name, allowed: [a-zA-Z0-9_-] chars
Invalid version, should be like: x.x.x
Invalid stability
Invalid date, should be YYYY-DD-MM
Invalid channel URL
Empty authors section
Empty package contents section
Is there any solution for this. Thanks
The magento modules downloaded from the magento connect have package.xml file with it, which verifies the module's whether it was downloaded from Magento connect or not.
All Magento versions > 1.5 support the extension key of magento connect version 2.0. While selecting key from Magento connect, please check the extension key must be of magento connect version 2.0.
I hope, it will solve this will help you. :)
If you are getting error from Magento connect, you can directly install the extension by downloading the extension zip and copy extension files in magento root directory.
you can download extension directly from the following site:
http://www.tangkoko.com/direct-download-magento-extension/
Paste magento connect key there.
Hope this help !!
Related
I'm leery of just installing community extensions, even with my version control. Is there a way to get the tgz so I can unpack it and inspect the extension before installing it?
As described on this site, Magento Connect 2.0 has a specific format that is easy to decipher. 1st get the Magento Connect 2.0 key. Example:
http://connect20.magentocommerce.com/community/Raveinfosys_Deleteorder
Then go to Magento Commerce website for that extension to find its version in the Release Notes tab. For this example, the latest version is 1.0.3
Now, combine the original key into this URL:
http://connect20.magentocommerce.com/community/Raveinfosys_Deleteorder/1.0.3/Raveinfosys_Deleteorder-1.0.3.tgz
I specifically use this command to download the extension to my work's internal server:
wget http://connect20.magentocommerce.com/community/Raveinfosys_Deleteorder/1.0.3/Raveinfosys_Deleteorder-1.0.3.tgz
... and then I'll normally make changes to those files to fit our template, ie change from default/default to default/my_template. Once I'm all happy I re-tar these files, scp the new tar-ball to my live site, and tar -xzvf via the ssh shell at Magento root.
I don't use magento connect... probably should, just can't bring myself to "trust" it blindly.
Or to make generic:
http://connect20.magentocommerce.com/community/Package_Name/[ver]/Package_Name-[ver].tgz
Some websites offer the links or proxied links to download any mangeto package from mangento connect as .tgz file (that is a gzip'ed tar-file). You get the standard magento PEAR package then.
These sites require the Magento Connect key to obtain the package:
Direct Download Magento Extension Without Pear (Tangkoko)
Download Magento Extension (http://freegento.com/) (only latest package version)
The first site offers a link to the package on the Magento Connect web-server, so that you can see how it works.
For Magento Connect 2.0 it is also written about how it works in a blog-post and there is a bash script that shows it pretty well on github.
After several attempts I have succeed to packaged one extension by using instructions from this PDF - http://info.magento.com/rs/magentocommerce/images/packagingmagentoconnectextensions6%200.pdf
Everything looks good, but when I try to upload the extension, it throws an error, saying that the filename should be in the format XXXXXX-1.0.0 format without the extension, where xxxxxxxxx is my form key, but when I try to upload the renamed copy of the packaged file (one that Magento connect manager extension generated), it throws these 2 errors:
An error occurred during upload to channel MagentoConnect 1.0: Unable
to upload new release XXXXXXXXXXXXXXX-1.0.0.tgz
An error occurred
during upload to channel MagentoConnect 2.0: Package
AnattaDesign_AbandonedCarts not found
I did a bit of research on the error and got to know this has been an issue with Magento in the past and people were facing the exact same issue. On some of them, I found #rondata replying back who was the community manager in back those days, but not sure if he still is.
So any clue how can I get this issue resolved? Whether it could also be an issue with how I packaged the extension? Or may be who is the current community manager and where can I seek some escalation on their uploader bug?
So I think I know what the reason is. When you are asked for the extension key when creating a new extension on magentocommerce.com, don't add the form key over there as your extension key. It's meant to be something unique like Namespace_Module.
When you do that, the error should go away and you should be all good!
I copied the website files of a live magento website to my local machine. I try to open the home page and a blank white screen turns up.
In the apache2 error log, I find the following line:
PHP Fatal error: Call to undefined function kYESppcDEoBrEZyw() in .../httpdocs/app/code/local/Aitoc/Aitoptionstemplate/Model/Observer.php on line 11
The culprit line is:
if(Aitoc_Aitsys_Abstract_Service::initSource(__FILE__,'Aitoc_Aitoptionstemplate'))
{ kYESppcDEoBrEZyw('e71e3cbbed8235b2be55dfb8db045b91');
and the other bracket closes at the end of the file.
It seems there is an extension called Aitoc custom options template installed. That's fine but what is the purpose of the strangely named function? And how is it working on the live site?
Any leads will be appreciated.
We need to be careful here since the website uses 3rd party extensions and the extension protects its license - it doesn't allow using the extension without installing the license first and throws the above error.
So you'll need to install the license on the local/dev server first before starting work on the website. You can also disable the extension(for AITOC) and get the website working by following the instructions at:
http://www.aitoc.com/en/magentomods_custom_options_templates.html#docs
I did disable it and I am able to run the website on the dev server.
I had the same issue.One more extension was installed in my site "Custom Product Preview".
So some files were missing while installing the extension.
When we uploaded the same missing files.Then refreshed the admin section.It asked for the license information after providing license information everything worked fine.
So be careful while installing the extension.
Also install the license carefully.
For me "/app/code/local/Aitoc/Aitsys/etc/compilation.xml" was also missing.
I'm trying to update the Joomla version on one of the website I managed.
I downloaded the package to upgrade to Joomla 1.5.25 (if my memory's good). I did a test on a dev website and everything worked well.
Now, when I apply the update to the current website, i receive the error : Fatal error: "Class JController" not found in */components/com_content/controller.php "
The line
jimport('joomla.application.component.controller');
is there.
Anyone has any idea?
Thanks a lot
try to upload the files again via FTP client. Sometimes files don't transfer properly or at all. Also make sure you downloaded the correct upgrade package related to your previous version.
But all I get from my Connect Manager is the following message:
community/Mage_GoogleShopping: Version for 'Mage_GoogleShopping' was not detected
If I try and use the version 1 extension key all I get is:
Couldn't resolve host 'magento-core'
I am using a mostly fresh install of Magento Community 1.5.0.1 (I say mostly because we do have our own template but it is very basic).
Anyone have any luck installing this extension. GoogleShopping is a huge boon to our hit count and the recent changes to the google products API has really affected our implementation.
this extension is still in alpha stability, you need to change your preference settings ("settings" tab in your magento connect manager) for "preferred state"
OSdave had the right answer ... but the way I fixed the error message was I blew away the download folder on the server and re-copied over from the original Magento install package.
Once I had done that I re-ran the Extension Key in Connect and this time it actually said. "That Extension is in Alpha stage. You'll need to change your preferences to install it."
I did NOT get the error above anymore. At that point everything worked like a charm.