Has anybody ever tried to integrate OXID into an existing PHP/MySQL enabled website somewhat ‘plugin’ style? That is, the existing website is still the primary server of pages but eShop functionality (basket, coupons, checkout, etc.) is added where wanted using the OXID core.
I saw the TOXID module but I think this still requires OXID to be the base platform. In my case, the client wants to keep the existing site and just add-on an eShop.
I know I could add the complete shop in a sub-directory and just adapt the template to resemble the main site, but this level of integration seems pretty poor. Essentially two sites that don’t interact with each other outside of links.
Anybody ever try to get a deeper level of integration into an existing PHP site such that, for example, a basket widget could be added to existing pages? I have some ideas in mind but thought I’d see what others out here think.
I think it would be way easier to install Oxid in a subfolder and use TOXID to integrate seemless all needed elements and functions of the shop into the main page. The visitor will never have the chance to identify which parts are from the original site and which come from the shop.
TOXID can be used in two ways - the shop as master, or the typo3-system (wordpress, Joomla - whatever) as master. In your case the shop will be the slave and just delivers services for your main site.
Check out those references and as well the Demoshops linked below the navigation.
That sounds promising but how does OXID ‘service’ the information in this case? When OXID is the master, my understanding is that the CMS feeds OXID the content in XML format to be included into templates and this is accomplished via TOXID cURL. But if the CMS is master, how do OXID templates/content get fed to the CMS? Does TOXID include some sort of web service for OXID that converts templates to XML? I’ve read something about a TOXID OxAPI but I though it wasn’t finished.
yes, we also have a demo, where - in our case - TYPO3 is the Master and the shop runs as an plugin. But thats kind of tricky, because you had to deal with the session.
In that case you should explain a bit more about the target system and setup.
How would you deal with authentification? What, if a user is not yet logged in but want to add something to the basekt (in that case you had to simulate a user-object),…
I’m interested in more informations.
Joscha
[QUOTE=spurvis;82648]Has anybody ever tried to integrate OXID into an existing PHP/MySQL enabled website somewhat ‘plugin’ style? That is, the existing website is still the primary server of pages but eShop functionality (basket, coupons, checkout, etc.) is added where wanted using the OXID core.
I saw the TOXID module but I think this still requires OXID to be the base platform. In my case, the client wants to keep the existing site and just add-on an eShop.
I know I could add the complete shop in a sub-directory and just adapt the template to resemble the main site, but this level of integration seems pretty poor. Essentially two sites that don’t interact with each other outside of links.
Anybody ever try to get a deeper level of integration into an existing PHP site such that, for example, a basket widget could be added to existing pages? I have some ideas in mind but thought I’d see what others out here think.[/QUOTE]
yes, we also have a demo, where - in our case - TYPO3 is the Master and the shop runs as an plugin. But thats kind of tricky, because you had to deal with the session.
In that case you should explain a bit more about the target system and setup.
How would you deal with authentification? What, if a user is not yet logged in but want to add something to the basekt (in that case you had to simulate a user-object),…
I’m interested in more informations.
Joscha[/QUOTE]
Can you supply a link to the demo which uses TYPO3 as the master?
Sorry, I’m not yet on the same page. Can’t yet understand these issues because I don’t know how the plugin is made possible. I downloaded the demo but the README only describes use with OXID as the master. There’s a note that says “NO Single-Sign-On (so no restriced pages are possible) See TOXID with OxAPI”, but where do I go to see more info on TOXID with OxAPI?
I’m guessing this OxAPI is what I would need to use but need to first understand how it works before I can grasp why there will be issues with sessions, authentications, etc. Is there a write-up/post anywhere giving an example of how a piece of OXID (such as the basket) would be [I]plugged[/I] into other pages?
the TOXID API-Version is not released yet as there is only a working demo and nothing where one should base a project upon. Its a case study, that shows, how it WOULD and that it WILL work.
the TOXID API-Version is not released yet as there is only a working demo and nothing where one should base a project upon. Its a case study, that shows, how it WOULD and that it WILL work.
What system do you want to use?[/QUOTE]
Ah, I see. I don’t think I could use it in this case then with the current client. However, I’d be interested in learning more for future cases. When a demo becomes available, that I can download and install locally, I will try it out.
Not sure what you mean by system. PE/CE or O/S? In any case I’m using CE on a Linux distro.
[QUOTE=spurvis;82900]Ah, I see. I don’t think I could use it in this case then with the current client. However, I’d be interested in learning more for future cases. When a demo becomes available, that I can download and install locally, I will try it out.
Not sure what you mean by system. PE/CE or O/S? In any case I’m using CE on a Linux distro.[/QUOTE]
Hi,
there will be code to download in the future (will also be linked at toxid.org). But this might take some time.