#292201

Re: HTML problem in XOOPS and Other CMS?

2002/7/5 10:04 It's really normal that XOOPS put's your content a lot lower then you expect. Put al your code before your text on 1 line. Difficult, but it works. XOOPS makes from every hard enter <BR>. Don't expect more . Normally if you put all your code on 1 line your content wil be on the 2 second line. Greeetz,

Jan304

P.S.:Plz remove a bit from your message, we now it's long

#292202

Re: HTML problem in XOOPS and Other CMS?

2002/7/5 9:00 Hi,
the URL of the site where i am trying to post the article is

http://cardielos.nicewebs.net/modules/news/article.php?storyid=6

and the HTML code is

<table border="0" width="913" bgcolor="#FFFFFF" cellspacing="1" height="2194" >
<tr>
<td width="148" height="132">
<p align="left"> </p>
</td>
<td width="751" colspan="4" rowspan="3" height="443">
<p align="left">
[...]

#292203

Re: Account re-activation required on Profile email changes

2002/7/4 23:47 Quote:

Hear, Hear!

That would a great addition to the already great CMS. Security is always a concern on this wide world of global communities.

#292204

Re: Extending the Titles of Submitted News

2002/7/4 18:31 Thanks for all the help guys, I appreciate it much.

#292205

Re: Account re-activation required on Profile email changes

2002/7/4 16:34 Quote:
Totally agree.

#292206

Re: Account re-activation required on Profile email changes

2002/7/4 15:48 Yes this makes sense.
Maybe we can add the logic like this:
when a user changes his email, his account will be disactivated, and then an email with activation code will be sent to his new email.
It can be an option.

#292207

Re: Polish your theme CSS files

2002/7/4 15:25 Good point!
And as I found, most themes has suboptimized style.css file.
All theme developers should keep in mind that within CSS file, the order of tags is important. If you dont care about this, you may find the rendering is not as you expected. Also please note that within CSS file, same tag can be defined several times (as many as you like), and the latter will overwrite the former.

Example:

p td input {
font-size: 12px;
color: blue;
}

p {
background: #808080;
color: redl
}

when rendered, all p element (except that you have definitions for more concrete p elements (with class or id) will be rendered as red.

The general rule is following the html element tree, and the uplevel and general elements at the top, and class follows, and then id definitions.

The best practice:
1. the first definition should be always html, coz in the new standard, the parent of all the elements is html, not body. html can be viewed as canvas.
2. the second should be body element.
3. then general elements as div, p, td, input etc.
4. then specific definitions as
p.some
td.other
5. then comes id definitions as
div#content


I need reiterate one point:
please use all lower cases for elements (or tags as you like, though there are some different), which meands:
p instead of P
div instead of DIV

Seems i should post a normative css file as example. I'll do it a little later.

#292208

Re: Extending the Titles of Submitted News

2002/7/4 15:06 Yes you can change the character limit to larger, but please ba careful because this change may make the display messy esp when you use two column blocks. The default setting is 18 characters. For Recent News and Top Read News block, you can change like this:

open modules/news/blocks/news_top.php, within function b_news_top_show() (should be line 35-37):
change
if (strlen($title) >= 19) {
$title = substr($title,0,18)."...";
}

to
if (strlen($title) > 35 ) {
$title = substr($title,0,35)."...";
}

this way it displays 35 characters.

For other blocks, you can look into all files under blocks/ dir of the module, and change as you like. You should test to find the best character limit and it should be dependant on your theme. If you dont allow theme change, and use only one theme and the best the theme has fixed width, you can get the best result.

Try it, and be cautious.

BTW, you should know the max length of the subject is 80 characters. If you need change to longer, you can do , but the ultimate limit is 255 characters. The best you dont change, or seek help before doing.

#292209

Re: HTML problem in XOOPS and Other CMS?

2002/7/4 14:49 Could you set me the html and a testing url to me at goghs@eqiao.com. I'll look into it.
Extra whilespaces may be caused by your html codes.

#292210

HTML problem in XOOPS and Other CMS?

2002/7/4 7:45 Hi,
I am trying to map pages made in HTML inside the Section and news part of XOOPS. I have tried freecontent, it works fine, but in need the Search mechanism to work, which happens only with content insert in the database.
When i put HTML in XOOPS, it works almost fine, i just have a problem that i don't know how to solve.
XOOPS insert in the beginning of all the content a lot of empty space, which makes my content go down in the window and not being seen right from the beginning.
I Have made the test with others CMS link postknue and Myphpnuke ( and in this case it is worse because it don't respect tables and columns).
THe test only workd if the last version of PHP-NUKE where all the content where displayed correctly.
Does any one know how to solve this problem?

REgards,
Danyblue