Nerdpress.org

If you wonder about routing in OXID eshops or how the URL structure is here are some hints:

OXIDs MVC, well thats some kind of different naming and you have to get used to:

the M (Model) you find in /core
the V you find in in your templates in /out, there the main view is called the same as your controller, given the controller has a render() method.
/views/details => /out/[templatename]/page/details.tpl
the C (Controller) you find in /views (what? oyerywell!)
like /views/details.php

The routing itself is like so:
» read more

With some advanced scheduled-post-voodoo i successfully managed to publish this post already yesterday with some completely unrelated queries and no text. this was not intended – please accept my apologies :P

Anyway: In the footer of my magento shop we might have a summary of the shopping cart,
which i simply put in the footer.phtml template file:
» read more

I just started digging in the shop software magento for a project and set up the following development environment.

In this scenario development is done on two local machines while products and pages beeing already edited on the “Live”-Web-Server.
Git is used for version control and deployment. Also FTP SSH. » read more

I recently made my first OXID eShop module: OXID-manufacturer-text-mod
Which basically adds a long description field to the manufacturer.

This comes just as a normal textarea, as usual in OXID CE.
If you would like to add an Richtext Editor, you can purchase the fck Editor module
and install it, if you did not already.

After you installed the fck module your textareas of the basic shop are rich text.

But since the manufacturer long description comes from the module, you have to teach the fck module the new field.
» read more