1
carnuke
Setting blocks exclusively, ie; not 'view all pages' excludes system pages.
  • 2004/12/30 15:40

  • carnuke

  • Home away from home

  • Posts: 1955

  • Since: 2003/11/5


When setting blocks exclusivly ie, not using the 'All pages' option, the following system pages cannot be included because they do not appear in the 'visible in' selection list.

viewpmsg.php
notifications.php
edituser.php
userinfo.php

Therefore as an example: In admin>blocks administration, edit main menu. Using the 'Visible in' drop down, If I make main menu to show in selected pages, but NOT 'All pages' I do not have the option to make it available in these system pages. These system pages are only included if 'All pages' are selected.

This can lead to navigation problems, when any of these system pages are viewed.

This is a risky question to ask in case I have missed something basic here, or is there a fix for this?

2
rowdie
Re: Setting blocks exclusively, ie; not 'view all pages' excludes system pages.
  • 2004/12/30 16:13

  • rowdie

  • Just can't stay away

  • Posts: 846

  • Since: 2004/7/21


There's no fix that I've read about.

The drop down list only lists modules, not the individual elements of the system module, or even individual pages of a module. It's something that I'm hoping will be addressed in XOOPS 2.1/2.2

Rowd

3
carnuke
Re: Setting blocks exclusively, ie; not 'view all pages' excludes system pages.
  • 2004/12/30 16:40

  • carnuke

  • Home away from home

  • Posts: 1955

  • Since: 2003/11/5


Thanks for that confirmation rowdie, I'm going to experiment with building these system pages into custom blocks, that way they will be become selectable.

4
DonXoop
Re: Setting blocks exclusively, ie; not 'view all pages' excludes system pages.

This is one of my biggest needs, an "all except xxx" block setting. Since I have a module or two that I didn't want left blocks on I enabled "All Pages" for main menu etc and then trapped the module name in my theme and then not do the left block loop for the selected modules. A cheap workaround but does the trick.

Even better is to get the root pages like register.php etc into a page that you can control (tinycontent etc?). I'll be interested in hearing how that goes for you.

5
carnuke
Re: Setting blocks exclusively, ie; not 'view all pages' excludes system pages.
  • 2004/12/30 17:14

  • carnuke

  • Home away from home

  • Posts: 1955

  • Since: 2003/11/5


I see your workaround DonXoops. It gets messy after a few versions though. I gues one could use the theme changer module and make a dedicated theme with block calls for each module.

Yuc, it needs a core fix and that's the bottom line I think.

Login

Who's Online

185 user(s) are online (49 user(s) are browsing Support Forums)


Members: 0


Guests: 185


more...

Donat-O-Meter

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

Latest GitHub Commits