31
LionHeart
Re: What are "XOOPS Codes"?
  • 2006/1/20 4:20

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Thanks Lance!

I'm curious why there's an option to permit XOOPS Codes, or not, if there is no danger to it? Does it conflict with something, maybe?



32
LionHeart
What are "XOOPS Codes"?
  • 2006/1/19 20:16

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


This is going to sound like a really stupid question, and maybe it is, especially since I've been using XOOPS for a year and a half now, but searched this site, the FAQ, and can't find the answer.

What exactly are "XOOPS Codes"? Are they similar to the "BB Code", the [ xxx ] and [ /xxx ] codes?

Where can I find a list of all the XOOPS Codes?

What is the danger of enabling them?

In advance, thanks.



33
LionHeart
Re: REQ: A Theme Manager
  • 2006/1/10 20:01

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Quote:
You can show the themes block to a group, wich allows that group to select a theme.


Can you show me how to have the themes block available to group A, displaying themes 1 and 2, while also being available to group B, displaying themes 1, 2, and 3?

Quote:
Each theme should already have a css in it's directory.


Yes, it does, but it doesn't change the full image set that a module uses when you change the theme.

For example, newbb. If you change themes, you still have the same set of button images, regardless of what theme is being used.

I hope this is clear enough for you to understand, now.



34
LionHeart
REQ: A Theme Manager
  • 2006/1/10 5:06

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


I ran a search and didn't see this mentioned anywhere, so I'd like to request it; an option in the admin panel for 'Display Management', to take over these functions;

Templates Management
- Default
- Other templates
- Set permissions for a template to determine what groups get that template

Theme Management
- Default
- Other themes, which are available
- Set permissions for a theme to determine what groups can select it. Amongst other uses, it would allow a webmaster to run tests on a theme before permitting it out to general use
- Option for a themes/modules/ directory, so that each installed module can it's images and css files in either a 'default' directory or in each theme, to allow complete consistancy throughout a theme.

This would require an option in how a module installs, allowing for an option to install (automatically or manually) it's graphics files within a theme directory.



35
LionHeart
Re: [design] Which site
  • 2006/1/10 4:26

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


There's some pretty amazing themes in use, as shown by the great examples posted in this thread :)

Some thoughts came to mind;

1) This is the main XOOPS organization site, the primary. It's look should reflect that. While a lot of the sites posted here have some fantastic visual appeal, if you want a new person to have the first impression that XOOPS is a professionally produced product then the main XOOPS site should convey a professional impression. Get away from 'table borders' and use more white space to separate sections, headers should be very clean and crisp, make more use of different font sizes. Perhaps a top navigation bar for separating major sections so that you are free to use full-width below for sections that deserve more space than a cramped center-column. There's a number of excellent corporate-style themes already contributed here on the site which could be nicely adapted for a custom design. The colours chosen are less important than the style.

2) Since this is the main XOOPS site, it should also be something of a technology demonstrator. It should reflect cutting edge web technology, or at least current state of the art. I know that maximum compatibility is important for the maximum number of users, and maybe that means there should be a theme switch to move between [PLAIN] and [EDGE].

3) I was really impressed by the Zen Garden's examples of what CSS is capable of (thanks Herko!), and I think that this sort of approach could be used to good effect, not just to make the site look better, but as part of the 'technology demonstrator', showing what XOOPS can do with CSS discipline.

4) There's a number of sites that I've admired, but whatever XOOPS uses should be unique to XOOPS. This software isn't like every other package, the site should reflect that uniqueness.

5) The new logo looks great, but using a commercial font forces any graphics designers who want to contribute fully consistant logos or banners either have to purchase the font, or steal it. This seems like an inappropriate position to place people into when all they want to do is contribute their time and talent to a community effort for a free software package. I hope the choice of font is reconsidered.

Just some notions, I hope they're of use.



36
LionHeart
Re: VisitorMap - count nothing
  • 2006/1/7 18:44

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Can someone tell me where to find the XOOPS compatible version of this module, it looks incredible



37
LionHeart
REQ - Module Recommendations for XOOPS 2.2.3
  • 2006/1/7 3:49

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Can anyone recommend modules that function 100% with XOOPS 2.2.3? It'd be great to see a version compatibility field in each download here on the XOOPS site.

In particular, I'm looking for a good recommendation for a fully functioning News module, and a Chatbox module, that both work with the 2.2.3.

Any suggestions will be greatly appreciated.



38
LionHeart
Re: Updated to News Ver 1.44 not TOP PAGE not display
  • 2005/12/28 3:40

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


This module is doing the exact same thing on my system.

My work-around was to set the News module as the Top Page, because Recent News will display on the News module's page.



39
LionHeart
Re: Missing Theme Block Data
  • 2005/12/24 23:24

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Updating the System module fixed it, Stew, thank you very much . Do you know if all the v.2 templates compatible with the 2.2.3?

I hope you and yours have a wonderful holiday!

-Lion



40
LionHeart
Missing Theme Block Data
  • 2005/12/24 20:20

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


I'm having a problem with a clean XOOPS installation;

I'm using a fresh installation of XOOPS 2.2.3, using the default theme. I'm trying to setup a System Theme block to be able to change the theme of the site. The block title displays, but there's no selection box beneath it.

I'm getting this error:

Warning [Xoops]: Smarty error: unable to read resource: "db:system_block_themes.html" in file class/smarty/Smarty.class.php line 1084

The file does exist at;

modules/system/templates/blocks/system_block_themes.html

and had a permissions setting of 744 just like the other files in that directory. I changed the permission to 755 and 777, but neither one fixed the problem.

I have not cloned the Templates or tried to do anything with them except to look inside at what System Templates were present. There was no template for 'system_block_themes.html', I don't know if that has anything to do with the problem.

Any ideas on this would be greatly appreciated, thanks in advance, and happy holidays!

-Lion




TopTop
« 1 2 3 (4) 5 6 »



Login

Who's Online

257 user(s) are online (146 user(s) are browsing Support Forums)


Members: 0


Guests: 257


more...

Donat-O-Meter

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

Latest GitHub Commits