I currently finished writing a payment plugin for opencart. I uploaded it using filezilla to an online opencart site, tested it and it worked perfectly.
After which i tried installing the same plugin using the extensions installer from admin, setup my ftp and i got a "installed successfully" message.
The problem is i can't find the extension under payment extensions in the opencart site. As in, it is completely missing but it definitely has to be somewhere since it installed successfully
NOTE
The previously installed plugin through filezilla cannot be possibly crashing with the new one because i removed that one completely.
I setup my FTP perfectly.
I zipped the upload folder, saved it with upload.ocmod.zip before uploading it.
How do i find the missing extension and if i'm installing it the wrong way, what is right way to go about the it.
In OpenCart 2.3, all extensions are listed in the Extensions > Extensions area. You then have to choose which extensions you want to filter on (e.g. Shipping extensions).
Which Opencart version you are using?
Related
Now that Mozilla requires Firefox extensions to be signed, I've decided to only host my personal extensions at the official Add-ons for Firefox (AMO) site. Previously, I hosted my extensions at my personal website, using the requisite update manifest machinery.
I'd like to redirect users who installed my extensions directly from my personal website to the new versions at AMO. I was under the impression that if I released an update of my extension without the custom updateURL in the extension's manifest, that it would check AMO by default. That doesn't seem to be the case, however.
How can I make it so that users who installed my extension via my personal site can get updates going forward from the official add-ons site? Are they essentially forced to uninstall / reinstall to pick up this change? Or can I trigger it somehow?
I should point out that the extension ID for my extension is the same, regardless of my distribution point. This is one reason I thought that simply removing the updateURL from the installer manifest would do the right thing.
Update: Here's further details on the scenario I'm trying to solve:
User installed version 2.6.5 of my extension from my personal website some time in the past.
I released version 2.6.6 of the extension on my personal website, removing the updateURL node from that version's installer manifest in the process.
I release version 2.6.7 of the extension on AMO only. I expect that the user from step 1 should be able to automatically upgrade their install to 2.6.7, but this isn't the case. It's as if Firefox doesn't know to check AMO for that given extension, even though the extension ID is the same.
Update 2: My installer manifest for version 2.6.6 contained the updateKey node, but not the updateURL node. When I remove the updateKey from the installer manifest, repackage the extension, and install it, the updates available at AMO are then found successfully. This shifts the problem, however, to the update manifest on my website. In order for an extension update to be found via my website, it needs the updateKey (unless I'm missing something obvious). How can I automatically push an update to an extension that (a) isn't hosted on AMO and (b) has neither an updateKey or an updateURL present in its installer manifest?
If you have your extension hosted on AMO, it will be automatically updated for the user (unless the user has 'Automatic updates' turned off for your particular add-on via Tools > Add-ons > Extensions > (your extension) > More.
And yes, you should remove the updateURL tag from your install.rdf file.
You can find more information at the MDM site.
i'm trying to install a magento extension in magento 1.8.1 community edition, but magento connect hangs at installing extension. the package is downloaded into the app/code folder, but doesn't appear to go any further. no error log entries created (there's an existing system.log, but no exception.log).
i've reset permissions per: http://www.magentocommerce.com/wiki/groups/227/resetting_file_permissions
then i tried too install manually with "./mage install http://connect20.magentocommerce.com/community [name_of_module]"
but downloader/lib/Mage/Connect/Command/Install.php on line 71-73 sets up $config->magento_root=dirname(dirname($_SERVER['SCRIPT_FILENAME'])); but the value seems to be blank (I'm guessing magento connect configures that somewhere)
how can i get either magento connect to work, or alternatively manually install the extension?
First, generate the download link for the extension using http://freegento.com/ddl-magento-extension.php
In order to obtain a download link, you have to generate a valid extension key in Magento Connect.
After manually downloading the extension, just unzip its content into Magento's app directory
Clean the cache and reload magento's main page, the extension should appear in administration under System->Configuration->Advanced
Hope this helps
Bye
I've been working on a website by building it on Joomla. I built it locally with XAMPP and today I copied the files to the directory on the FTP to publish the website and went to the admin panel and there are no plugins or templates, this is weird because I copied the whole folder and imported the database. Already did this twice but it seems to be another error than copy error.
Attention:
I did not install the template and plugins after getting the joomla online, I just copied it to the ftp
Your best bet is to use a tool like Akeeba Backup. This will automate the process and resolve most common issues when moving a Joomla site.
I have recently downloaded a copy of Magento version 1.7.0.2 and upon opening it up in Netbeans there is a red explanation mark on that folder. I have only seen this symbol on my own code to signify that there is an error in the code (i'm doubting this is the case as it Magento).
The files that are displayed as having an error are:
app/design/adminhtml/default/default/template/catalog/product/attribute/js.phtml
app/design/frontend/base/default/template/checkout/onepage/shipping_method/available.phtml
app/design/frontend/base/default/template/checkout/onepage/billing.phtml
I have uninstalled and reinstalled my copy and still have this problem, is this heard of by anyone else? or is it a Netbeans thing?
Also under the folder:
app/code
the only folder there are community and core. In This post a local folder is mentioned. Is this something you need to add manually or should it be there on the install?
I have a Joomla site running on a windows machine. The site was at 1.6 when some update requests came in. I decided to update the site, but the automated process didn't work, so I started FTPing the files up there manually.
I followed the instructions for the manual upgrade at http://docs.joomla.org/Upgrading_1.6.5_to_1.7 once I got the site to 1.6.5, but my problems had already started before that.
Now when I go to mysite.com/administrator most images are not there and when I try to log in I get kicked up to my site root rather than the /administrator folder. I took the opportunity to look at the code and none of the image src attributes or the form action attributes include "/administrator".
Soooo I need a little advice as to why this is happening. I would rather not have to restore from my backup and start over at 1.6. I was kinda hoping for this to be my first Joomla 3 site. Thanks in advance.
You said that you had trouble with updating Joomla via the admin panel, however did you check if the folders were writable? Site -> System Information -> Directory Permissions Always check this page once you have installed Joomla as it is the reason why a lot of people are unable to install updates or normal extensions.
You then mentioned that you had to upload the files manually via the FTP, however this is not requires. All that is required it to upload the update.zip to the foot of your Joomla site and unzip it.
As for a proper answer, May I suggest that you first update to the Latest version of the 1.6 series (1.6.6), then you download a fresh copy of Joomla 1.6.6, unzip the "administrator" folder, zip that folder, upload via the FTP to your Joomla root folder, then extract it. This will override all the default administrator files.
In the end I had this client move their Joomla install off Windows and onto a Linux machine. Things were just getting worse with the install and I threw in the towel. Thanks to Lodder for trying to help.
This can happen if you are using the JSecure plugin. It requires a token in the URL to enter the admin panel, for example:
http://www.yoursite.com/administrator?token
Explanation:
http://forum.joomla.org/viewtopic.php?p=2198164
I was able to fix this by removing the value that I had in the $live_site variable in the configuration.php file. I am also running this on a Windows server.