1
LeeStewart
Re: What can I do in the "site closed" template?
  • 2004/9/6 23:12

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


Quote:
tjnemez wrote:
for myself it is a very simple process to edit the templates. you can copy and paste the code from the template into your editor.
That's not really a "simple process" if you're working on a couple different templates and the CSS file. My PHP editor will automatically upload changed files - that's a simple process.

I was hoping there were some files that I could edit and upload instead of dealing with the database version of the templates - sure it'd be slower, but it would speed my development up.

When I have a moment, I'll try to hack something that will use files when developing a template and then load them into the database for production mode.


Thanks for confirming my suspicion,
Lee



2
LeeStewart
What can I do in the "site closed" template?
  • 2004/9/6 17:17

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


It seems the system_siteclosed.html file has some limits and I'm trying to figure out what they are.

For example, it looks like the meta tags aren't being expanded for this page. Also I can't populate the login name using $block.unamevalue. The $xoops_url variable is filled in, but things like $xoops_themecss aren't?

I want to make this page match the rest of my site and don't want to duplicate a ton of html and CSS. Is there a pointer to what's avaiable?

Also, is there an easier way to modify system_siteclosed.html than using the admin screens to edit/upload the file? Is there a local version that I can edit and FTP to my web server?


tia,
lee



3
LeeStewart
Re: Are Smarty comments {* *} available?
  • 2004/9/6 17:08

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


Quote:
The nice thing about Smarty comments is that they don't waste bandwidth
Yeah, I totally agree. I was saying that there are times when you're creating a module that you might want to see these comments. In other words, it would be cool if Smarty would convert them to HTML comments when running in debug mode.

Hardly worth mentioning, since it's easy to work around. Mostly I'm tying to post enough so I can upload my own avatar. :)



4
LeeStewart
Re: Are Smarty comments {* *} available?
  • 2004/9/1 22:50

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


Quote:
Xoops redefines the Smarty delimiters as <{ and
Doh! I just read through some sample theme files and saw that.

I searched this site, but didn't spend enough time digging through the code...

<{* I'm a knucklehead... *}>


Quote:
I think it's better to use Smarty comments than HTML comments, since that way the comments get stripped off earlier.
Actually, an even better option is making it configurable - like another level for debugging.

When making your own templates it might be useful to see those comments, but in a production environment they're just wasting bandwidth.


Thanks for the resonse,
Lee



5
LeeStewart
Are Smarty comments {* *} available?
  • 2004/9/1 22:18

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


I was wondering if it was possible to remove the HTML comments that I'm using with Smarty template comments:

<!-- HTML Comments -->

{* Smarty Comments *}


I tried it on theme.html, but it desn't seem to work. Is that functionality disabled?


tia,
Lee



6
LeeStewart
Re: News 1.2 upgrade borked?
  • 2004/8/30 3:04

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


I poked around and found that the problem occurs when the user approves an article and $this->storyid isn't set. When this happens, the SQL performs an INSERT instead of an UPDATE and things go weird from there.

While I was tracking down the problem further (why is the storyid unknown? is it not being set in the hidden form variable?) I started having some other problems. I'm not sure if they're related, but even a simple UPDATE causes the xoops_stories table to get locked...



7
LeeStewart
Re: News 1.2 upgrade borked?
  • 2004/8/29 16:10

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


Quote:
What's your Mysql's version ?

I'm running an older version on my test machine: MySQL 4.0.0-alpha-nt. I've never had problems with records getting locked, but I read something about it on a webpage. I ran "repair" on the table and that seemed to fix things. I'll see if the problem pops up again.

If there's any chance this might be a problem in the News module code, I can take a look at it. If you're 100% sure it's a MySQL problem, then I'll try it on my production machine running MySQL 4.0.20.

My shoe size is 10 (USA).



8
LeeStewart
Re: News 1.2 upgrade borked?
  • 2004/8/29 15:05

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


Hervé, thanks for the quick response.

I went into phpmyadmin and looked at the tables, I saw that xoops_stories was "in use", a state I've never seen before. This is a test server, so I just nuked the tables and reinstalled News. Everything was working great.

Then I broke it again.

I have two users, one that has permission to create news articles and the webmaster, who can approve articles. I logged in as the webmaster, wrote a news article and approved it. Everything was fine.

When I use the other account (who can't approve articles) to create a news post and then logged in as the webmaster to approve it, the xoops_stories table got stuck in the weird "in use" state.

I can provide any info you might need, template details, MySQL&PHP versions, my shoe size, whatever...

Thanks,
Lee



9
LeeStewart
News 1.2 upgrade borked?
  • 2004/8/29 3:33

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


I installed XOOPS 2.0.7 and upgraded the news module to 1.2. I followed the upgrade.txt file - overwrote the existing news folder and updated the module in system admin -> modules.

When I went into the Topics Manager in the News module preferences, I didn't see an "upgrade" link.

I only had a couple news articles and they used to appear with no problem. Now they seem to be gone. I tried every combination of permissions and other options and still no luck.

When I turn on debugging and view my news page, I see
SELECT COUNT(*) FROM xoops_stories WHERE published=0
Error number
1016
Error message
Can't open file: 'xoops_stories.MYD'. (errno: 145)

Did I make a mistake with the upgrade process? Anyone else see this?


Thanks for any pointer,
Lee



10
LeeStewart
JavaScript error in admin Control Panel
  • 2004/8/29 2:51

  • LeeStewart

  • Just popping in

  • Posts: 10

  • Since: 2004/8/29


I'm not 100% sure of the cause, but there's Javascript problem on IE 6 (probably other browsers as well). My development machine is set up to display errors - I can ignore the problem and it continues fine.

I reproduce the problem by going to the admin Control Panel and clicking the yellow buttons on the left. Sometimes a page is loaded and there's a problem with the PHP Layers Menu (layersmenu.js): Error on line 25 - Object Expected

The problem is on the underscored line:
} else if (IE4 && DOM && !Opera5 && !Konqueror) {
    [
b][u]currentY += document.body.scrollTop;[/u][/b]
}

As a test, I added a line before that:
} else if (IE4 && DOM && !Opera5 && !Konqueror) {
    if (!
document.bodyalert("what the heck?");
    
currentY += document.body.scrollTop;
}

The alert() pops up every once in a while - it looks like this JavaScript callback is being executed before the page is fully loaded.

To get around the problem, I check for the existence of the document.body object before dereferencing it:
} else if (IE4 && DOM && !Opera5 && !Konqueror) {
    if (!
document.body) return
    
currentY += document.body.scrollTop;
}

I'm not sure if anyone else has run into this, but I thought I'd share with everyone...




TopTop



Login

Who's Online

193 user(s) are online (114 user(s) are browsing Support Forums)


Members: 0


Guests: 193


more...

Donat-O-Meter

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

Latest GitHub Commits