parent child information pages [SOLVED] :D

artcore wrote:I say create a module so you can just echo it in the header or footer or anywhere you feel like

controller>module>information_menu.php
Add all your custom stuff from header controller in here
End with
return $this->load->view('default/template/module/info_menu.tpl',$data);

module folder>info_menu.tpl
html markup with data

OCMOD 2 files[/]
In header controller
$data['info_menu'] = $this >load->controller(module/information_menu)

In header tpl: echo $info_menu; at a nice spot

Minimum core changes FTW

still needs to add tables in the db and alter current tables

OSWorX wrote:Please do not do it that way!
Leave the original tables as they are and create new.
Combine them when needed, that way the original system stays intact and in case the extension is not needed anymore no troubles will arrise!

thx.

masterbeta wrote:

OSWorX wrote:Please do not do it that way!
Leave the original tables as they are and create new.
Combine them when needed, that way the original system stays intact and in case the extension is not needed anymore no troubles will arrise!

thx.

ocmods can create/alter table as well as remove so that is no problem - but to make a module vs extension, not sure how to accomplish that...

either way, i figure this information pages hierarchy should be a base setup for oc
not an extension or mod - should be out of the box already in oc from the beginning.... not sure why the devs didn't include it that way to start with...

Thx for pointing me that way .. but I guess I have made more modules - also vq- & ocmods - than many others here

Anyway, modifying core db.tables is never a good way for an extension.
What if the shopowner does not want your extension anymore?
Now you have to alter the database tables again ... nonsens.

Better to create a new table and call from there what you want/need.

Discussing here if that should be in the core or not - is useless.
Create an extension (best OCMod if) and publish.