I had installed a magento extension for cashu payment gateway.Earlier I could see it on the backend as well as on the frontend. Later I uninstalled it. Cashu support team gave me correct version of extension to install it manually. But this time I could see the extension only in the backend but not in frontend. What could be the possible reason for this and how do I fix it. Thanks!
Related
Installed Fishpig's Wordpress plugin on my Magento (1.7) site.
I would like to know how to :
install Disqus with Fishpig's Wordpress extension
remove the default comment section.
I've tried playing with the Universal Code from Disqus and have installed the plugin in Wordpress but nothing is showing up.
To use Disqus comments on your Magento/WordPress integrated blog, you first need to install the Disqus Comments plugin in WordPress, which is a free plugin. Next, configure your Disqus account via the WordPress Admin. You can use this to import any existing comments in WordPress into Disqus.
To get your Disqus comments to show on your integrated blog (in place of your default WordPress comments), you will need the FishPig Disqus extension for Magento. This extension takes your Disqus account details from WordPress and displays the necessary code to display the comments in your Magento blog. The extension will do this automatically and you won't need to configure anything in Magento for this to work.
http://fishpig.co.uk/magento/wordpress-integration/disqus/
If after installing the Disqus comments extension the comments do not display, the first thing to check is that you are using the latest version of Magento WordPress Integration. If you aren't, upgrade to the latest version.
If this doesn't fix the problem, check whether you have the wordpress.xml layout file or any wordpress templates in your custom theme. If you do, rename them so that the new version (in base/default) is used. You may need to refresh your Magento caches after doing this.
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.
I've upgrade my joomla version 1.5.26 to joomla version 2.5.4 and all the things has been upgraded successfully. So when i goes into my joomla module manager admin panel then it is not showing me any kinds of modules which was previously visible in my old version(1.5.26) but in my frontend panel it can be seen easily.Does anyone knows the solution how to fix it?
When you said you migrated, I assume you used an extension such as jUpgrade.
Migrating will update the core file and database tables and thus should show all the core Joomla modules in the Module Manager, however it does not upgrade your 3rd party extensions, therefore you will need to download the Joomla 2.5 compatible versions. This upgrade however, should be showing your core modules in the list.
I hope you took a backup of your 1.5 site. If you did, trying running the upgrade again and if you didn't use jUpgrade, I suggest you do so.
Hope this helps
make sure you're using the standard template for joomla. Go to module manager, choose Administrator in the first filter, and see if all modules are published in actual module positions (i.e. cpanel, status, footer, icon, login, menu, submenu, toolbar I guess that's it for administrator)
I want to write an extension that is compatible with Magento Go ...
There is anything in particular to know about Magento Go on the dev side ?
Your module should be reviewed by Magento team. See more here - Trusted Magento Extension.
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.