i just switched to oxid and wanted to test the community edition. The items for this shop have a lot of information. So the designer decided to make several subpages for each item. In fact the only thing that changes is the text.
How do I create a 2nd, 3rd… page for the same product?
How do I create custom fields for products (only found threads about problems with creating custom fields but no real description how to do it in the first place).
How do I create my own language file? We want to add french as 3rd language and I am kinda stuck with that.
How do I create a 2nd, 3rd… page for the same product?
[/QUOTE]
Are these different classes of informations? Maybe a solution would be to add more tabs?
[QUOTE=bsc;59661]
2. How do I create custom fields for products (only found threads about problems with creating custom fields but no real description how to do it in the first place).
[/QUOTE]
Sorry - I am no coder
Maybe another solution for having more content for the articles would be to connect to a cms like typo3? You could implement the content from typo3 into the shop.
First page will display some normal features, 2nd page will display technical information, 3rd dealer information… It is connected to questions number 2, i just want to have different fields for each product in the table and display them on different pages.
I dont want to integrate another CMS. As far as I know you can add columns to the product table in the database. I can do that but I dont know if I have to do something special or give them special names etc.
Furthermore those fields need to be editable in the admin backend. I am also not sure how to get them there…
[QUOTE=bsc;59681]1. First page will display some normal features, 2nd page will display technical information, 3rd dealer information… It is connected to questions number 2, i just want to have different fields for each product in the table and display them on different pages.
[/QUOTE]
Hi bsc,
adding the fields in backend and frontend of the shop isn’t that hard. Just add the collumns in your database in the oxarticle table.
Because of the lazy loading, they should be directly available in the framework (just cleare the tmp-folder once), after you call them in your templates. Saving in admin should also work “out of the box” after you put your fields into the admin-template.
