151
fatman
minimum admin cp requirements
  • 2003/12/16 21:51

  • fatman

  • Friend of XOOPS

  • Posts: 176

  • Since: 2003/12/13


Hi. I'm constructing my first module which will have a simple admin side. As far as assembling the admin portion of a module is there anywhere which outlines the a preferred method of organizing files?

The wiki doesn't go into the admin side of things. I've looked at several other modules and think the minimum I need to do is the following

in /admin/index.php

include("../../../mainfile.php");
include_once(
XOOPS_ROOT_PATH."/include/cp_functions.php");
xoops_cp_header();
// main admin logic
xoops_cp_footer();


That works fine for me, just want to make sure I'm not missing something critical, specially for security.




152
fatman
Re: semi-Static content module
  • 2003/12/16 5:56

  • fatman

  • Friend of XOOPS

  • Posts: 176

  • Since: 2003/12/13


wow, thanks for the quick reply. I just installed wf channel and it's pretty close to what I need. Certainly worth using and not recreating the wheel.



153
fatman
semi-Static content module
  • 2003/12/16 5:21

  • fatman

  • Friend of XOOPS

  • Posts: 176

  • Since: 2003/12/13


Hi all. First time poster. I was wondering if someone knows of a module or method to do the following, or if I should just write the module myself.

I need a method of organizing what would just be 'static' pages in a non dynamic site. Things like About Us, Legal, Terms of Use, ect..

I want this content to be in the database, and I would provide a simple admin menu for adding/editing pages. I don't want to physically have files that need to be managed, so I I'm not sure the Freecontent module is what I want. If it is please let me know.

Following is a rough draft of the info I would manage for each page.

pageid
pagename - (for index.php?pagename )
pagetitle
page desc
page body
page author
date created
date updated

My module would simply look at the page name being called and then load the page details into a very simple template.

I would not add any categories or structure to the module as I would anticipate a tie in with a universal category system.

So that all being said. Do the xoop experts think I should hack something already made, or build something simple that I can tie into other global classes later?

BTW: I'm very impressed with XOOPS so far and I'm excited to give it a test with a new project I just landed :) I've been looking for something to organize my own modules better and previous systems just didn't cut it. I really like the direction XOOPS seems to be heading.



154
fatman
Re: Block positioning question?
  • 2003/12/13 18:56

  • fatman

  • Friend of XOOPS

  • Posts: 176

  • Since: 2003/12/13


One suggestion would be to enable the definition of custom block locations. In the site prefrences somewhere I could add names for custom block locations. Then in my main theme.html I could define any location I want that block to show up in.

Then locations like center, left, right ect would just be the default custom block locations.




TopTop
« 1 ... 13 14 15 (16)



Login

Who's Online

137 user(s) are online (94 user(s) are browsing Support Forums)


Members: 0


Guests: 137


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Dec 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits