PostNuke

Registration in 0.64 doesn't only add the info users input when registering into the table $prefix_users. It also adds the name of the default theme, and quite possibly the default number of stories on the main page.

So: never change the name of your default theme. If you want a new theme as default, delete the old theme and name the new theme the old name (use the find/replace function to change the name of all the links so they go in the right directories). And don't take changing your default number of stories lightly.

If you have already changed your default theme, you can remedy this by putting copies of this same theme in your themes directory, with the different names (again, remember to change those links). Or if you just delete the old themes, users get the default theme--I didn't like this option since I wondered about possible bugginess or loss in processor time. Or you can make a dump of your db table users and edit everybody's theme to default. No, edit users doesn't let you mess with your users' themes. It should, as a means available for punishing naughty users--give 'em a really irritating theme and make them change back. Or give 'em one with a parse error, and as long as they don't reset their cookies, they are denied access!! Btw, you can always do this if you just edit your table _users and throw in that buggy theme.

A suggestion for futher PN versions: theme and number is not submitted to the db at registration, and only when users explicitly change themes--otherwise it's default.

The core still needs some work. There's this, there's search's requiring the admin's name in the db to return results. There's the hyperbolic stats module. A ton of applause to the dev team for all the sweat they've already put into PN. Let's cool off when it comes to asking for new features and let them get the core perfected.

This little story dedicated to Talen who helped me find this glitch--btw, Talen, welcome to postnuke.

but doing this brings about another question... shouldn't the title of each page vary as you move through the site? For example, a setting in each module to allow for page title --- Since my site deals with Memphis, shouldn't itbe able to pull up as a title for my article on the lights and festivities at Graceland "Christmas with the King" or some such, then my personals module should be different to incorporate FREE memphis personals for singles in the memphis metro area and my trouble ticket module should also have Memphis computer help desk as the page title? This brings another cool thought... Each module should have a section in the admin where one can write a paragraph of fluff and copy relating to that module... The reason for this is very simple... Search engines that read for content... Of course, I could always make a master include file... but am looking for a long term solution...

Any thoughts?

http://www.memphisweb.net/

I will make my include and header.php available to any who contact me thru the memphisweb contact form.

Taking from the $ModName trick which is often used in the modules you can add the following line:
$thename = basename( dirname( __FILE__ ) );
This reads the theme's directory (just like PostNuke does) and inserts it into your theme's links and image tags.
Thereby allowing the site manager to change the theme's name (the directory name) without actually editing the theme.

Am I right that this is not a feature of Postnuke? How difficult would it be to implement? Has anyone done developed such a tracking and analysing package for an existing site?

The idea is to have one (or more) top level 'Layout Blocks' which are represented in t

Feel free to mess around with the layouts etc. but please be gentle, this is only a wee box.

This is only the admin side (there'll be a 'preview' option vsn...) but hopefully it will demonstrate the proposed flexibility, not just in the layout on the main page, but also for the blocks nested within the main page.

This will also give the option of different layouts for the same theme, depending on the context (op=? or name=?).
The browser as html tables.

Each cell can have one or more Layout Blocks or normal PN block nested inside it.

• The first page of the demo shows a listing of defined Layout Blocks, each displaying their 'grid model'


• At the foot of this page you have the option of creating a new Layout Block.


• Select a cell and press [Define Cell] to define it's width and height (col/rowspan).


• Press [Define Content] to define the blocks to be nested within the selected cell.


• To add new content press [Add Cell Content], otherwise select the required content and press [Modify Cell Content].

Comments (especially from PN core team), bugs and complaints (observations) much appreciated. (Don't forget this is prototype code, so not all exceptions are handled cleanly...)