Ravens PHP Scripts: Forums
 

 

View next topic
View previous topic
Post new topic   Reply to topic    Ravens PHP Scripts And Web Hosting Forum Index -> WYSIWYG - Raven's RavenNuke(tm) v2.x Distro
Author Message
erald
New Member
New Member


Joined: Dec 13, 2004
Posts: 21

PostPosted: Mon Sep 18, 2006 1:28 pm Reply with quote

Ok I have tried to find any word on the font size changes which are not displayed in articles when using the wysiswyg editor.
I found remarks about the fact the css file is overriding the size changes. However it is funny that color changes are not overridden.
Also I have an older version running (not raven distro, but standaard phpnuke 7.5) with fckeditor 1.6 and you know what have no problesm with it at all. although I use the same theme and when looking at the source of the text it looks the same.
So somewhere somehow thinks do not work out in this distro.
If I change the font size or the font, the css seems to overide it in this distro in my older installations it does not. I wonder why?

Erald
 
View user's profile Send private message
kguske
Site Admin


Joined: Jun 04, 2004
Posts: 6383

PostPosted: Mon Sep 18, 2006 2:35 pm Reply with quote

The font size (like some other attributes) can be overriden by the theme. They are not overridden by Nuke or the RavenNuke distribution. Are you using the same theme for both? If the same content is in the database in both versions, I'd compare the themes to see where the differences are.

_________________
I google, therefore I exist...
Only registered users can see links on this board! Get registered or login!
 
View user's profile Send private message
erald
PostPosted: Mon Sep 18, 2006 2:57 pm Reply with quote

Then I do not understand earlier messages sorry..
However I tested it with the same themes like the nuke theme and several others. I did use the same content with some big fonts and on the raven distro it was always to the defined css font size in the theme, where it was not the case in the older installation (7.5 nuker with 1.6 fck)
Also I use the standard theme coming with the raven distro and when trying to change the font size it is overidden by the default.
So if you say it is not then I have a serious problem with my installation somewhere. I do have it on two different raven installations which where both clean new installs.
Off course I can overide it by using classes I define in the style sheet and put those in the source. but WYSIWYG is not really WYSIWYG thi s way..
So if you have any idea why this is happening I would be gratefull.
 
kguske
PostPosted: Mon Sep 18, 2006 3:16 pm Reply with quote

The best way to confirm what's happening is to compare the content in the database. If the content in the database is the same, but doesn't appear the same, with the same theme, I'd guess there was something strange going on with the installation.

The 2.2 version of FCKeditor could treat things differently than 1.6, and the early FCKeditor integrations with PHP-Nuke did not address HTML filtering. Since nukeWYSIWYG isn't installed by default in RavenNuke (at least not until the next release), I'd recommend checking to make sure all the files were changed correctly, including the config.php file, which contains allowable html used by the kses HTML filter in nukeWYSIWYG. If the right HTML isn't allowed, it will be removed from the content before storing it in the database (hence the recommendation to compare the database content).

Other than that, I can't thing of anything but the theme that would cause RavenNuke to display the same content differently than your older installation.

Remember that PHP-Nuke allows multiple themes, so even if it were WYSIWYG, it wouldn't necessary mean that it's WYSIWYG for all themes. That's one of the reasons we didn't focus too much on integrating nukeWYSIWYG with CSS. It would also be very difficult to do with all the different approaches theme and module developers use, and it's easy enough to circumvent by specifying the class.
 
erald
PostPosted: Mon Sep 18, 2006 4:13 pm Reply with quote

Ok there is no difference in the database.
It is not loosing the font size setting but just not displaying it. If I look at the source of the webpage it looks the same (well have not gone through everything.)
But still it is not displaying it.
example:

<font size="5">testing</font> gives in the editor a bigger font, in the preview and when posting it will use the font size defined by the content class in the css file..

the webpage source looks the same in both:

<font class="content"><font size="5">testing</font></font>

for some reason this does not work this way I should be able to override the default font size defined in the content class.
what could be the problem?
 
kguske
PostPosted: Mon Sep 18, 2006 4:27 pm Reply with quote

If the HTML is the same, the themes must be different - or at least the style sheets. Search the HTML source for css to see what's different. At least we know it doesn't have anything to do with kses filter or the version of FCKeditor. I wish I new more about CSS - maybe others can pitch in here.
 
erald
PostPosted: Tue Sep 19, 2006 5:11 pm Reply with quote

Ok After looking over the obvious and searching on the wrong places I found what the problem is.
In the style sheet there is one difference in the first line where the font definition is
In de new distro it says:
FONT {FONT-FAMILY: Verdana,Helvetica,sans-serif; FONT-SIZE: 10px}

change this to
#FONT {FONT-FAMILY: Verdana,Helvetica,sans-serif; FONT-SIZE: 10px}

and the problem disapperes. You can then use the font size with the fck editor and it will then be displayed. Avtually that goes for all attributes from which some do not work.

I am no css specialist and have no idea why. Might be others know why this happens.
Been comparing the output of the pag with and without and there is no difference what so ever.
actualy this problem exsists in all themes coming with the raven distro. I have a site using an older version of reaven distro and there the # is in front of the FONT definition.
Why has this been taken out in the last distro??
 
malrock1
Hangin' Around


Joined: Nov 04, 2006
Posts: 47
Location: Wanaka New Zealand

PostPosted: Tue Feb 27, 2007 9:17 pm Reply with quote

Wicked!

I love it when a problem is solved by searching ...
cheers erald

_________________
Life's a rock
go climb it
Only registered users can see links on this board! Get registered or login! 
View user's profile Send private message
kguske
PostPosted: Wed Feb 28, 2007 6:49 am Reply with quote

I don't remember discussing that in the RN changes. It's possible that we started with fresh copies of the themes so we could work on compliance issues - I know Montego spent a lot of time on that.
 
Gremmie
Former Moderator in Good Standing


Joined: Apr 06, 2006
Posts: 2415
Location: Iowa, USA

PostPosted: Wed Feb 28, 2007 10:35 am Reply with quote

Putting a # in front of Font means that that style will only apply to an element that has the ID="font". So essentially you are removing the default style for font tags by doing that. I would imagine you'd get the same effect by commenting out that line (with /* */) or even deleting it.

<font> is not a "cool" tag anymore...you should use div and span instead.

_________________
Only registered users can see links on this board! Get registered or login! - An Event Calendar for PHP-Nuke
Only registered users can see links on this board! Get registered or login! - A Google Maps Nuke Module 
View user's profile Send private message
Gremmie
PostPosted: Wed Feb 28, 2007 10:42 am Reply with quote

I suspect that with a FONT style in your CSS, a font tag with a size="" attribute isn't enough to override the style. Font is kind of deprecated by CSS and the two probably should not mix.

And I meant to say <font> is not cool, you should use <div> and <span> WITH CSS instead.
 
montego
Site Admin


Joined: Aug 29, 2004
Posts: 9457
Location: Arizona

PostPosted: Thu Mar 01, 2007 7:14 am Reply with quote

erald wrote:
actualy this problem exsists in all themes coming with the raven distro. I have a site using an older version of reaven distro and there the # is in front of the FONT definition.
Why has this been taken out in the last distro??


I do not recall us making ANY style.css changes in any of the RavenNuke distributions prior to the upcoming 2.10.00 release. So, you are probably referring to Raven's older packaging of PHP-Nuke distros. If you see something missing, it was that we simply start with PHP-Nuke 7.6 and if it was missing in 7.6, it was "missing" in RavenNuke.

RavenNuke is NOT the same as Raven's prior distributions.

I'll have to check the 2.10.00 code to see what we have for the style.css files. Actually, fkelly and Raven has done most of the actual theme work. I worked solely within the non-theme code to get it to be XHTML compliant.

_________________
Only registered users can see links on this board! Get registered or login!
Only registered users can see links on this board! Get registered or login! 
View user's profile Send private message Visit poster's website
Mithoron
Hangin' Around


Joined: May 05, 2003
Posts: 34

PostPosted: Wed Apr 04, 2007 9:33 am Reply with quote

Came here looking for this exact same problem. At the top of my style sheet for my AcidTech style.css sheet I have:

FONT {FONT-FAMILY: Verdana,Helvetica; FONT-SIZE: 10px}
TD {FONT-FAMILY: Verdana,Helvetica; FONT-SIZE: 10px}

I actually have to rem out both to get the FCKEditor to use the Font Sizes on the front page; however, doing that also causes some issues with various other pages (such as the Admin Page listing all the News articles in obnoxiously huge text, hehehe).

Anybody have a better work-around on getting the Font sizes with the Editor to display correctly on the News section?
 
View user's profile Send private message
montego
PostPosted: Wed Apr 04, 2007 7:43 pm Reply with quote

Mithoron, do you also have a BODY { ... } tag in the CSS? If not, try copying either the FONT or TD one and change it to BODY and then comment out FONT and TD. Let us know how/if that works.

Also, in tons of places within Nuke, it uses the .content tag.
 
Mithoron
PostPosted: Wed Apr 04, 2007 11:14 pm Reply with quote

Yes, there is a body tag:

    body { padding: 0 5px; }


so not sure if you're recommending with changing it or not.


The content tag in this style sheet is:

    .content {BACKGROUND: none; COLOR: #ffffff; FONT-SIZE: 11px; FONT-FAMILY: Verdana, Helvetica}


but I doubt it's that as I can change the colors in the News section with the FCKEditor fine, it's just the font size that seems to be fixed.

One thing I have noticed is that changing the text to Header3 makes it a little bigger; however, just plain text I want to change the font size does not change on the site.


It's really no biggie, something I can live with, hehehe...was just searching the site for several issues I had and this one was one of them but not something I can't live with, LOL!
 
montego
PostPosted: Thu Apr 05, 2007 6:49 am Reply with quote

Well, then, I will let the editor experts handle this one... I really don't know what it is doing behind the scenes.
 
fkelly
Former Moderator in Good Standing


Joined: Aug 30, 2005
Posts: 3312
Location: near Albany NY

PostPosted: Thu Apr 05, 2007 11:12 am Reply with quote

I have posted over in our internal bug tracker. I'm recommending that we just take the font-size out of the font class in the style.css for fisubice. I've tested this on my test site at fkelly.org. It's a relatively easy change to make and if anyone else wants to experiment and report back ... does it solve your problem, does it cause any other problems. I tried removing the font size from some other common html tags in the style file (td, body, div etc.) but that caused problems.

We can do the same for other themes but it would be good to have some testing first. I've run thru most of the modules on my test site but I wouldn't describe it as extensive testing.
 
View user's profile Send private message Visit poster's website
Mithoron
PostPosted: Thu Apr 05, 2007 11:44 am Reply with quote

Would you totally remove the FONT tag or just the FONT-SIZE portion? Tried putting a # in front of the class but that did not seem to do anything...but that was only in one spot, never looked at any other style sheets...
 
fkelly
PostPosted: Thu Apr 05, 2007 11:52 am Reply with quote

I just removed the font-size portion. I believe that is overriding a font tag that the wysiwyg editor puts in.

Since I still have it open in my editor, here's what the line would look like:

Code:
font {font-family: Verdana,Helvetica,sans-serif}
 
Mithoron
PostPosted: Thu Apr 05, 2007 9:50 pm Reply with quote

FANTASTIC! Thanks fkelly, that did the trick!

Definitely makes a different to be able to use the full capabilities for the editor, much appreciated!
 
fkelly
PostPosted: Fri Apr 06, 2007 11:15 am Reply with quote

You are welcome mithoron. I started looking deeper at this issue for some future release. The book I use on styles, Head First HTML with CSS and XHTML, deprecates the use of fixed (pixel) font sizes in favor of using relative ones based on the body tag. So you'd say for instance:

Code:
body {font-family: Verdana,Helvetica,sans-serif; font-size:x-small}


then base your other font sizes relative to that. For instance,

Code:


input,textarea,select{border-color:#000000;color:#000000;font-size:110%}


I'm doing some experimenting with fisubice using that approach. It seems to work well in basic Nuke (the core modules that come with the distribution) but there is some strangeness with my Gallery application using that approach. It almost looks like they might take the same "relative" approach but be using extra-small or something even smaller.

So this is a work in progress where it pays to have a test system. I think we are really just in the initial stages of using style sheets to control layout in Nuke and I'm finding that it's a whole area of specialization that's not to be taken lightly.
 
fkelly
PostPosted: Fri Apr 06, 2007 3:52 pm Reply with quote

Just for kicks I tried this version of the fisubice style.css on my test site. I had to make adjustments because I found that Gallery used a percentage of the body style font-size that caused problems if you made the body style be font-size:x-small. Since most of the material within core nuke blocks is presented in td's having the x-small in there accomplishes much the same thing as having it in body.

This is completely experimental, back up what you have first and only try it if you are in an experimenting mood and want to give feedback here.There are very likely to be add on modules or even places within the distribution that may not work properly with this.

Code:
td {font-family: Verdana,Helvetica,sans-serif; font-size:x-small}

body {font-family: Verdana,Helvetica,sans-serif; font-size:small}
p {font-family: Verdana,Helvetica,sans-serif font-size:x-small}
div {font-family: Verdana,Helvetica,sans-serif font-size:x-large}
input{margin-bottom:2px;margin-top:2px;text-indent:2px}
input,textarea,select{border-color:#000000;color:#000000;font-size:110%}
input,textarea,select{background: #ffffff;border-width:1px; Verdana,Arial,Helvetica,sans-serif}
input.catbutton{background:#fafafa;color:#000000}
input.button{background:#fafafa;color:#000000}
input.liteoption{background: #fafafa;color:#000000}
input.mainoption{background:#fafafa;color:#000000;font-weight:bold}
input.post,textarea.post,select{background: #ffffff;color:#000000}
.helpline{background:#e1e9f2;border-style:none;color:#000000}
.code{background:#fafafa;border:1px solid #d1d7dc;color:#006600; font:11px Courier,"Courier New",sans-serif;padding:5px}
.quote{background:#fafafa;border:1px solid #d1d7dc;color:#444444; font:125% Verdana,Arial,Helvetica,sans-serif}
.bodyline{background: #f7f8fc;color:#000000;border:1px solid #98aab1}
body{background:#ecf0f6;color:#000000;}
.hidegoogle{color:#ecf0f6;font-size:0pt;}
hr{border: 0px solid #ffffff;border-top-width:1px;height:0px}
a:link,a:active,a:visited,a.postlink{color:#32475f;text-decoration:none}
a:hover,a.topictitle:hover{color:#839fbc;text-decoration:underline}
.title       {background: none; color: #000000; font-size: 140%; font-weight: bold; font-family: Verdana, Helvetica,sans-serif; text-decoration: none}
.content     {background: none; color: #000000; font-family: Verdana, Helvetica,sans-serif}
.block-title {background: none; color: #516A88;  font-family: Verdana, Helvetica,sans-serif}
.storytitle  {background: none; color: #516A88; font-size: 120%; font-weight: bold; font-family: Verdana, Helvetica,sans-serif; text-decoration: none}
.storycat    {background: none; color: #000000; font-size: 120%; font-weight: bold; font-family: Verdana, Helvetica,sans-serif; text-decoration: underline}
.boxtitle    {background: none; color: #000000; font-weight: bold; font-family: Verdana, Helvetica,sans-serif; text-decoration: none}
.boxcontent  {background: none; color: #000000; font-family: Verdana, Helvetica,sans-serif}
.option      {background: none; color: #000000; font-weight: bold; font-family: Verdana, Helvetica,sans-serif; text-decoration: none}
.tiny        {background: none; color: #000000; font-weight: normal; font-family: Verdana, Helvetica,sans-serif; text-decoration: none}
.small       {background: none; color: #000000; font-size: 90%; font-weight: normal; font-family: Verdana, Helvetica,sans-serif; text-decoration: none}
.sandersh1   {background: none; color: #990000; font-size: 180%; font-weight: bold; font-family: Arial, Verdana, Helvetica,sans-serif; text-decoration: none}
.sandersh2   {background: none; color: #990000; font-size: 160%; font-weight: bold; font-family: Arial, Verdana, Helvetica,sans-serif; text-decoration: none}
.sandersh3   {background: none; color: #990000; font-size: 140%; font-weight: bold; font-family: Arial, Verdana, Helvetica,sans-serif; text-decoration: none}
.sandersp    {background: none; color: #000000; font-size: 120%; font-family: Verdana, Helvetica,sans-serif; text-decoration: none}
.sandershr   {border: 5px;border-top-width:5px;height:2px}
img {border-style: none }
 
Mithoron
PostPosted: Sun Apr 29, 2007 6:36 pm Reply with quote

Unfortunately I haven't had time to test this out on our site. I don't have a backup site to do it on so have been a bit leery of changing things now that they're working, LOL.

Hopefully will be getting a test server here soon to try some of this out but curious to hear if other people have tried it out and got things going!
 
fkelly
PostPosted: Sun Apr 29, 2007 6:52 pm Reply with quote

Good thing. There are a couple errors with the code I posted, I left some semi-colons off after several of the font-families at the top of the code. I've been meaning to post a correction but just haven't gotten to it. There will be a fix for the basic problem in the patch release of Ravennuke (the fix just involves removing the font-size from the font class in the style). The notion of making all font sizes "relative" while supported by most of the literature on styles, remains purely experimental in practice. I had it running on my production site for a few weeks but I backed it off tonight because of a few scattered problems I saw.

If fellow developers want to weigh in or experiment with the notion of making the sizes relative then go for it. But if you are running a production site you'd be better to stick with the official RN releases.
 
montego
PostPosted: Mon Apr 30, 2007 5:51 am Reply with quote

Quote:

I backed it off tonight because of a few scattered problems I saw


Actually, this does not surprise me as there are still formatting HTML tags within nuke (even RN) that might cause issues here or there.

Such a shame too that if we "fix" RN, it is possible that many themes would now become "incompatible". Just a "gut feel" is all.
 
Display posts from previous:       
Post new topic   Reply to topic    Ravens PHP Scripts And Web Hosting Forum Index -> WYSIWYG - Raven's RavenNuke(tm) v2.x Distro

View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum


Powered by phpBB © 2001-2007 phpBB Group
All times are GMT - 6 Hours
 
Forums ©