I'm new to spree commerce and migrating from Magento. I was trying to integrate Mandril. What I found is this:
In Magento: Site => MangeMonkey Plugin => Mandrill
What I found in documentation for spree is this:
Site => Wombat => Mandrill
instead of:
Site => Mandrill Gem => Mandrill
Am I correct?
Now Wombat is a paid system which contradicts the 0$ policy of spree. My question is it a compulsion to use Wombat with spree?
Any blog link or suggestion for integration will be highly appreciated.
Thanks
you could easily override the rails default mailer and provide mandrill smtp credentials. using something like this https://github.com/renz45/mandrill_mailer
Related
Please help, I Want to use REST api in joomla 2.5 !! I searched a lot and spend many days in Github and techjoomla. I didn't get it how to install API extension or Plugin and use that...
Even I didn't find any proper documentation to use API. And from where to install It....
Can anyone please explain me step by step how to install API plugin with proper link to download them and proper documentation to use it please...
You mentioned that you are using Joomla 2.5 (which is no longer actively developed or supported). If it is possible for you to upgrade / migrate to Joomla 3.4.x, your options open up.
I ended up developing a RESTful API for Joomla 3.4.x, powered by the Slim PHP micro-framework. Please note that this is a commercial Joomla package, so if you were interested in "free", this isn't it.
The package includes the following:
Services Control Panel component
Joomla "services" add-on library which includes a version of Slim v2.6.2 (along with several other libraries) obtain via composer and normally found in the vendor folder. More on this later...
Services Joomla Plugin
Services REST Plugin
Services Slim Configuration Plugin
Slim JSON API View plugin
Slim JSON API Middleware plugin
You might ask, "What is the point of all these plugins?"
The answer is that it allows for compartmentalization of functionality of the core components and opens the door for an easily extensible services routes architecture. Note that new plugins could easily be added with Joomla ACL restricting access to those new routes, for example.
The Services Control Panel allows for creation of tokens on a per-user basis (or even multiple tokens per Joomla user). It also allows the end user to configure the Slim micro-framework parameters and even include a threshold for the API rate-limiting functionality (currently based on requests-per-minute). Actually, that part is totally awesome as it provides live feedback on the state of the API rate threshold within the response header.
The cAPI Core package ("cAPI", short for "Constant API" because everything needs a product name...) is just that - a core package. There is a host of add-ons currently in development, the first one being a secure LDAP JSON API (which connects to Microsoft Active Directory), with lots more cool add-ons to come.
The whole point of all this is to say that, basically, your request has been answered and now a commercially supported solution has finally arrived. Plus, instead of reinventing the wheel, I based the extension on a popular, existing micro-framework (Slim), making it easier for developers to work with or develop on the core, pluggable, framework.
So, you get the best of Joomla (robust ACL, advanced plugin architecture, wealth of extensions) and Sim (proven, standards-compliant, mature RESTful PHP micro-framework), all in one easy to install package.
Exposing a website via an easily queryable API should not be taken lightly. I would hope anyone choosing to do this would implement 100% HTTPS access and security-harden their server(s).
You can find more information here: http://getcapi.org
Hope this gets you going in the right direction.
Service Endpoints and CORS Ajax calls
/api/v1/user/ - Can be used to log a user in and out and returns the activated Joomla session in the response - This also provides for multimodal authentication (both via token in header or username & password in URL string). Basically, it works with your needs. - You force a user logout like this: /api/v1/user/logout/username/joomlasessionid
Basically, this is tailor-made for driving remote services or, say iOS or Android apps.
/api/v1/content/ - Provides basic ability to create, retrieve and update content - This functionality, while it exists, I would consider it under active development and will become MUCH more robust over time.
I have embedded a sample jQuery Ajax syntax followed by the html for the div container that can display the output. Note that the headers line is optional (depends on the requirements of the API).
jQuery('button').on('click', function() {
var requestUrl= "https://www.annatech.com/api/v1/slim/swagger";
var start = new Date().getTime();
jQuery.ajax({
url: requestUrl,
type: "GET",
success: function (resultData) {
totalTime = new Date().getTime() - start;
jQuery( "#title" ).empty();
jQuery( "#requestUrl" ).empty();
jQuery( "#totalTime" ).empty();
jQuery( "#output" ).empty();
jQuery( "#version" ).empty();
jQuery( "#output" ).append(resultData.info.description).html;
jQuery( "#version" ).append('Version '+resultData.info.version).html;
jQuery( "#title" ).append(resultData.info.title).html;
jQuery( "#requestUrl" ).append(requestUrl).html;
jQuery( "#totalTime" ).append(totalTime+ 'ms').html;
},
error: function (jqXHR, textStatus, errorThrown) {
alert('error');
},
timeout: 120000
});
});
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js"></script>
<button>Send CORS</button>
<p>Request URL: <span id="requestUrl"></span></p>
<p>Response Time: <span id="totalTime"></span></p>
<h2><span id="title"></span></h2>
<h3><span id="version"></span></h3>
<div id="output"></div>
It should go without saying that all cAPI Core package improvements are included in the annual subscription fee. Add-ons are (will be) billed and supported separately.
About Documentation
Please note that the documentation is still under development, but if you would like to contact me directly (or through https://www.annatech.com/annatech-llc.html), I can go over the details with you. Also, I would recommend that you look over the Slim micro-framework so you can understand the basic route design http://docs.slimframework.com.
Let me know if you have any other questions.
Does anyone see any roadblocks to routing a rails 4 app as a subdomain of an existing website made from Joomla?
Although they are different frameworks, I'm not trying to integrate the two apps. Just placing two different websites under a single domain. My thinking is as long as both applications are on the same server and I fixed my namespace in my rails routes file, all should be ok. Is my logic correct?
Yes, there are no problem, the only 2 things you have to care about are :
take care of the item menu in joomla
the ruby web server configuration
About the joomla item menu.
In the Menu Manager > Edit Menu Item as a Menu Item Type chose System Links > External Url .
In the Link field you can put your rails url.
With this configuration you can route your user to your rails app.
About the ruby web server configuration
Probably you already have your rails app running, so you are not worried about the web server.
But because you already have an Apache server for Joomla I guess It could be interesting for you know that like for php in Apache there is mod_php, for ruby there is Phusion Passenger.
And that's the discussion on Stackoverflow: Ruby on Rails Server options
With Facebook Upgrading to Graph API 2.x and the New Facebook Login.
Is it necessary to upgrade Facebook php SDK 3.2.3 to 4.0.0?
If it is not, how can I make change for Graph API 2.x base on PHP SDK 3.2.3?
Thank you,
Griffin
It isn't strictly necessary, but v3.2.3 has no support for specifying the graph API version you want to use.
If you are updating an app and want to use graph v2.0+ before Facebook forces it on April 30th, you'll need to use the v4 SDK or hack v3.2.3. I recommend you just bite the bullet now and use v4. v3.2.3 is deprecated anyways.
Please use latest facebook sdk,
because it old version will be closed.
See change log https://developers.facebook.com/docs/apps/changelog
sdk v3.2.3 (graph api v1.0) available until 2015/4/30
About php, you can upgrade the php verion to php 5.4
or try use facebook sdk for javascript.
There are another option, not very clean but... you can hack the class.
You can change
https://graph.facebook.com/
to
https://graph.facebook.com/v2.0/
in
base_facebook.php
Be aware with deprecated dates
https://developers.facebook.com/docs/apps/changelog
The cleanest way I found is to modify $DOMAIN_MAP outside of the vendor code and before you use the Facebook API.
$version = 'v2.3';
BaseFacebook::$DOMAIN_MAP = [
'api' => 'https://api.facebook.com/' .$version . '/',
'api_video' => 'https://api-video.facebook.com/' .$version . '/',
'api_read' => 'https://api-read.facebook.com/' .$version . '/',
'graph' => 'https://graph.facebook.com/' .$version . '/',
'graph_video' => 'https://graph-video.facebook.com/' .$version . '/',
'www' => 'https://www.facebook.com/' .$version . '/',
];
I am creating a real state website with joomla 2.5, but I am facing problem with the Facebook login integration. Can anyone suggest me which module or plugin to use?
Use component JFBConnect. It will support in Joomla 2.5
there is also a good and cheap extension Facebook All and also free extension avail now
I wrote a web service and deployed it on Glassfish 3.1 but I am not able to see the link 'View Endpoint' link under 'Action' column. I am using the 'Glassfish 3. 1 Administration Tool' at 'http://localhost:4848/' under 'Application' under 'myapp'. After getting the web services deployed, I do see the 'webservices' added under the column 'Engines'. I need that link for finding 'Web Service Endpoint Information' so that I could see the WSDL and test the web service using Tester feature given by Glassfish 3.1.
Could someone help me understand whay am i not able to see that 'View Endpoint' link under the 'Action' column in the 'General' section.
Thanks.
That's how it worked for me:
Check if web.xml exist in your project (possible it is in webapp/WEB-INF/web.xml).
Delete web.xml.
Restart GlassFish server and "View Endpoint" link will appear.
I had the exact same issue - when I stopped and restarted the Glassfish server, the "View Endpoint" link appeared. Not sure if that will work for you, but it did the trick for me.