11
LionHeart
Re: REQ - Update WF-Quotes?
  • 2006/10/24 13:36

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


That's an interesting idea... all the basics are in place for it, I think, with the Random Question block in SmartFAQ. It would take changes at the developer level to make it work, I think. Too many things that wouldn't fit, even with a global name change on the title of the module. But certainly the SmartFactory Team would do a fantastic implementation if they chose to pick it up, based on their other modules.



12
LionHeart
Re: theme page selection
  • 2006/10/19 2:51

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


James... Thank you. Very much. I'm not a coder either, still blaming it on the trauma I suffered from not being able to get a 3-line 'hello world' program to work with the data-corrupted Atari ST Basic disc years ago, lol. After much trial and error, I finally got it figured out and it's working perfectly in moving to the proper template for the given module, and staying there when I drill down.

What I wasn't understanding was that I had to specify the variable in each OR statement. This is what it finally came down to;

<{if $xoops_dirname == 'newbb' || $xoops_dirname == 'smartsection' || $xoops_dirname == 'myalbum' || $xoops_dirname == 'popnupblog'}>
    <{include 
file="Classic/theme_other.html"}>
<{else}>
    <{include 
file="Classic/theme_main.html"}>
<{/if}>


I really appreciate your patience and support, James, thank you once more.

Now I can move on to fixing the next problem!



13
LionHeart
Re: theme page selection
  • 2006/10/18 18:37

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Hi James,

That's a really good point regarding the page titles, they can change when you drill down into some of the module options, and then the theme dumps back into the theme_main.html, which is no good.

I looked for the variable you used on thehttp://xoops-tips.com/news-article.storyid-12.htm site, but didn't see it.

$xoops_requesturi


Is that from a non-english language file? And if so, I can I use it in an english template? Or is there another name for it? I tried to use it exactly as you typed it, and it didn't work (I also tried 'requesturl' in case that was a typo, but it didn't do anything at all).



14
LionHeart
Re: theme page selection
  • 2006/10/18 14:31

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


I found the answer!

In case others need to do something similar, I'll post it here. It's the use of the ELSEIF statement. It looks like this, in the theme.html;

<{if $xoops_pagetitle == Forums}>
    <{include 
file="Classic/theme_other.html"}>
<{elseif 
$xoops_pagetitle == Journals}>
    <{include 
file="Classic/theme_other.html"}>
<{elseif 
$xoops_pagetitle == Library}>
    <{include 
file="Classic/theme_other.html"}>
<{elseif 
$xoops_pagetitle == Gallery}>
    <{include 
file="Classic/theme_other.html"}>
<{else}>
    <{include 
file="Classic/theme_main.html"}>
<{/if}>


This directs my full-width modules to the full-width theme_other.html, while everything else goes to my page with side-blocks eating up some of the screen real estate, on theme_main.html. ELSEIF creates as many options or alternative theme layouts as I need.



15
LionHeart
Re: theme page selection
  • 2006/10/18 13:56

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Hi James,

The ! parameter is good to know, it may come in handy, but in this case I think it puts me back where I started from, only reversed.

I have 4 exclusion statements that I wish to insert in the IF statement, and then all ELSE goes to main. What I need to figure out is how to have all 4 of them in place. I'll explain the layout, maybe that will make more sense;

In the template header menu (across the top), there are 5 options. 1 is for the Main menu. The other 4 are the Forums, Library, Gallery, Journals. These other 4 options are full-screen display modules, no left or right side blocks, and the template is different to make that work correctly.

However, in the Main menu, there should not only be the News module, but the Polls, Guestbook, Downloads, Links, etc (all are small-display modules), all of which should display in the Main menu (Main menu retains left and right side blocks).

The way it is now, everything except the News will go to the full-screen display. The only modules which that should happen to are the 4 options in the header menu.

Is there a way to have 4 parameters in the IF exclusion statement?

Something like;

<{if $xoops_pagetitle == ForumsLibraryGalleryJournals}>
    <{include 
file="Classic/theme_other.html"}>
<{else}>
    <{include 
file="Classic/theme_main.html"}>
<{/if}>



16
LionHeart
theme page selection
  • 2006/10/18 1:00

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


I'm trying to set my theme so that when any of header-menu (across the top) modules are selected, the theme goes to 'theme_other.html', but any other time, stays in 'theme_main.html'.

Looking over the theme.html file, I see this;

<{if $xoops_pagetitle == News}>
    <{include 
file="Classic/theme_main.html"}>
<{else}>
    <{include 
file="Classic/theme_other.html"}>
<{/if}>


Can anyone show me how I change the statement to look something like this, instead;

<{if $xoops_pagetitle == Forums}>
    <{include 
file="Classic/theme_other.html"}>
<{if 
$xoops_pagetitle == Library}>
    <{include 
file="Classic/theme_other.html"}>
<{if 
$xoops_pagetitle == Gallery}>
    <{include 
file="Classic/theme_other.html"}>
<{if 
$xoops_pagetitle == Journals}>
    <{include 
file="Classic/theme_other.html"}>
<{else}>
    <{include 
file="Classic/theme_main.html"}>
<{/if}>


I know the above change doesn't work , but that's essentially what I'm trying to get to. Can anyone show me what the code should look like, to get there?

In advance, thanks!



17
LionHeart
Re: REQ - Update WF-Quotes?
  • 2006/10/17 15:54

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Or if no one wants to fix the old WF-Quotes beta, perhaps someone out there can recommend an alternative?

It seems incredible that XOOPS lacks such a basic feature in the current versions, I'm sure there has to be some functional alternative out there which I am unaware of.



18
LionHeart
Re: Changed theme folder = White page for all themes
  • 2006/10/17 3:57

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Debug was on, permissions were correct, and I dumped the cache directories (except for the index file), nothing helped.

Since the site is a fairly new install and I was still configuring, after a day of frustration, I deleted the installation and started from scratch. Everything's fine now, I just wish I knew exactly why XOOPS went south on me, and how to bring it back if it happens again.



19
LionHeart
Re: Changed theme folder = White page for all themes
  • 2006/10/9 16:20

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


Hi Snowy

I restored the folder name to "Classic", updated the System module, made sure the themes were properly selected, but no joy.

I went into the database and checked, theme_set has "phpkaox" in it, as it should. Still a white-screen.

Good ideas, thanks for thinking on it!



20
LionHeart
Changed theme folder = White page for all themes
  • 2006/10/9 2:55

  • LionHeart

  • Just popping in

  • Posts: 70

  • Since: 2005/5/14


XOOPS Version: 2.0.15
PHP Version: 4.4.4
MySQL Version: 4.1.21
Web Server Software (Apache/IIS/Other): Apache/1.3.37
Operating System: Linux
Theme you are using: phpkaox
Custom template: (Yes/No) No

A full description of the issue:

This is a fresh installation, only a few days old. Modules are installed, and a theme designer is working on a custom theme for me. I have phpkaox set as default.

The designer sent me the latest build, the theme name is "Classic". I wanted to install the latest build alongside the earlier one, so that we could compare the update, so I renamed the themes in the directory (and I think this is where I screwed it up). I renamed the earlier builds to "Classic01" and "Classic02", and renamed the latest build to "Classic03". I enabled the themes in preferences.

I think tried to go back to the home page, and got the 'white screen'. I back-paged to return to the admin. I went to the System module and updated it. I created a new template set and selected it, as a just in case (probably too late, but it was a shot). I deleted all the files from template_c/ except for the index.html. I checked to make sure that no module caching was enabled.

Nothing helped. I still have a white screen, even the default theme comes up white.

I searched here, and the only thing I could find was a note that said, "Don't rename the theme folder or bad things will happen". I think I've found the 'bad thing'. :(

Please, anyone, help? Any ideas for fixing this?




TopTop
« 1 (2) 3 4 5 6 »



Login

Who's Online

203 user(s) are online (129 user(s) are browsing Support Forums)


Members: 0


Guests: 203


more...

Donat-O-Meter

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

Latest GitHub Commits