Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
5 - 4 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
   

Re: Pico installed but some module menus are blank? Is this expected behaviour?
by Brendahoisin on 2008/1/16 11:51:04

OK - I bit the bullet and went ahead anyway...

Thanks guys. The options finally appeared in Pico module admin when I cloned the templates and switched over to them in Preferences.

Yippeee!
Re: Pico installed but some module menus are blank? Is this expected behaviour?
by Brendahoisin on 2008/1/16 11:45:57

OK Madfish, I'll give this a go. But first...

How do I clone the XOOPS default template set?
Do I uninstall Pico before I start this and then reinstall it?

I've already been managing my templates through the Altsys module since I installed it, but it hasn't changed the symptoms as described in this post.
Re: Pico installed but some module menus are blank? Is this expected behaviour?
by MadFish on 2008/1/16 6:54:38

Try:

1. cloning the XOOPS default template set.
2. Set the new copy as your current default (in system => preferences =>general)
3. Then install pico and generate the templates manually as I described earlier.

Hopefully that will get you going. If it doesn't, GIJOE recommends that you manage templates through the Altsys module instead. I've never tried it, but see Peak XOOPS site for details.
Re: Pico installed but some module menus are blank? Is this expected behaviour?
by Brendahoisin on 2008/1/16 0:38:33

"Then, from your module front page, you create categories and page's content."

That's the problem - I can't. I know I should be able to do this (especially as it all worked fine with TinyConent) but I'm still getting blank screens in the admin menu - I guess I still haven't got the templates in yet.
Re: Pico installed but some module menus are blank? Is this expected behaviour?
by damaster on 2008/1/15 21:50:27

Most D3 modules are frontend based. That means, we define module config from admin side: groups/user permissions, filters, wrap and rewrite url, fckeditor or XOOPS default, etc. Then, from your module front page, you create categories and page's content. You can also personalize language variables, export templates with smarty and define an history (diff) for your documents edition.

You can add an ajax library by category or by page (header), override css and even made forms. Basically, you can create almost any type of content. Personally, Pico is my favorite module and for sure the greatest module for... not so static content^^

Have Fun !

Who's Online

222 user(s) are online (158 user(s) are browsing Support Forums)


Members: 0


Guests: 222


more...

Donat-O-Meter

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

Latest GitHub Commits