关于 CSS 的话题,由于我的主题宽度固定,我不得不将字体大小减小并将菜单宽度从 160px 减少到 100px 以放下四个下拉菜单。谁能告诉我为什么在 Internet Explorer 中下拉菜单会这样做;
当在 FireFox 中下拉菜单这样做时;
您会注意到每个菜单左侧的绿色向下箭头图像紧贴边界,就像在 FireFox 中查看那样,但当我们用 Internet Explorer 查看,这个绿色的向下箭头图像会向右偏移大约 15 像素,这强迫“主题选项”和“搜索论坛”菜单占用两行,看起来非常混乱。我已经仔细查看 CSS,但我找不到可能导致这种情况的缺失内容。有人有任何建议吗?
错误发生 SELECT t.*, u.name, u.uname,u2.name as last_post_name, u2.uname as last_poster, p.post_time as last_post_time, p.poster_name as last_poster_name, p.icon FROM xoops_bb_topics t LEFT JOIN xoops_users u ON u.uid = t.topic_poster LEFT JOIN xoops_bb_posts p ON p.post_id = t.topic_last_post_id LEFT JOIN xoops_users u2 ON u2.uid = p.uid WHERE (p.post_time > 1091055022 OR t.topic_sticky=1) AND t.forum_id = AND t.approved = 1 AND p.approved = 1 ORDER BY topic_sticky DESC, p.post_time DESC 如果页面没有自动重新加载,请点击此处
sorry marko, but i did not found the time and possibility to play with the modultemplates and files of newbb2 and 2nd i wanted to wait for a stable release not to work so many times at same place if there's a change in version and templates.
I hope i got the content of this discussion correct..
my first thought was ... it's funny to see that nearly every new module will use his own stylesheets and css-files ... baah, i will quit my job ... for i'm used to have my stylesheets in a central place.
(wasn't that ONE advantage of css??) Of course, i use more than one css files during parsing a theme but.. mostly find in one folder on a server ... (hope that not every module dev will load his css from different locations ??)
and i am a member of the old generations who is of the opinion that the only place to load a stylesheet is between the head tags of an [x]html document. In this case it is the theme.html
Where is your css loaded? (u use @import or jscript?)
marko, normally style.css (or other named.css) is loaded first and then your newbb.css so why to look Quote:
for a way to import the css color from style.css to the newbb.css ?
if you don't overwrite those classes in the style.css with your settings, classes and id's are active ?
Of course you may use @import url within a css file and load other instances but why? (if this will work in dynamic file structure for there are some diferent themes round?) Shouldn't we be fair and discuss+define what kind of definitions to load from which css file?(if there is no other way than that?) Or discuss new class and id structure?
... some thoughts to avoid from loading css fom other places than head: if there is the need for the module dev to have his own css (for positioning in that box e.g.) can we have ONE NAME and PLACE each module please to give the possiblity to load in theme on event using @import url(pathtoactivemodule/module.css); perhaps we can optimize to identify if there is the need to load an additional modulcss
Sorry for beeing rude today, i'ts late night here and my wife is on citytour with some friends whereas i had to look after our sons ....
... I know that this won't help you in this moment, but i will have a look into this .. michael
Re: NewBB 2.0 RC3 release
phppp:Quote:
have you updated the module?
Yes I updated the module.
Re: Topic Options
Predator:Quote:
You are using still the old templates, please delete them in your used templates set and generate them new.
OK, I deleted the three files from my server but then they're not available in the template set manager. How do I regenerate them?
Perhaps I don't understand your instructions.
Note that in the following list, the numbers 16 and 8 next to Forum and Community News are red while the others are black. (I couldn't figure out how to paste a screen shot into this editor.)
o Events [List (1)] o Contact Us [List (1)] o multiMenu [List (3)] o Downloads [List (11)] o Web Links [List (11)] o Forum [List (16)] o Community News [List (8)] o System [List (26)] o XoOgle [List (4)] o BookStore [List (11)] o FAQ [List (2)] o Headlines and Emails [List (3)] o Members [List (2)] o Partners [List (3)] o Polls [List (4)]
Is that significant?
Re: Topic Options
@damjam
sorry when the instruction was not clear, you don´t have to delete them from the server, you just have to use the template manager in the admin interfac.
Go to you used templateset there you have the choice edit,delete, download to each template, here you use delete and after you have deleted all templates from the newbb you have now the choice to generate them.
@michael
we should have a talk tomorrow via ICQ if you don´t mind
Re: Topic Options
Quote:
you don´t have to delete them from the server
Already deleted them from server. Fortunately I still have my local copy of RC2 and could restore them.
Quote:
here you use delete and after you have deleted all templates from the newbb you have now the choice to generate them.
I followed this procedure. All but six files were regenerated. The six that weren't gave a message that the "selected file does not exist". But I confirmed that these files are indeed on the server. Here are the files: newbb_post.html newbb_preview.html newbb_quickreply.html newbb_block_active.html newbb_block_new.html newbb_block_top.html
Notably, these six files remain from RC2 and were not updated with the installation of RC3.
My forum looks better now, except for the styling issues discussed by others here. Are those six files not needed?
Re: Topic Options
Quote:
it's funny to see that nearly every new module will use his own stylesheets and css-files ... baah, i will quit my job ... for i'm used to have my stylesheets in a central place.
I also like to have a centerized stylesheet.
One of the reasons that new modules use individual module-wise stylesheet files is that it needn't change the existing themes, especially if a user has some themes and if he is not familiar with css. From a regular user's point of view, I think using the newbb.css is simplier than changing the theme/style.css/styleNN.css
Perhaps this is why the $xoops_module_header is introduced?
Re: Topic Options
@damjam, if possible, make a temporary admin account and I could take a look at your newbb.
Re: Topic Options
Thank you. I'll pm you the login info. Do you have AIM?
Re: Topic Options
Damjam don t feel alone I have the same problem
Re: Topic Options
@phppp,
reading my sentences after some hours of sleep you are right.
yes .. a view in source ... will have saved some time ..
Quote:
... I think using the newbb.css is simplier than changing the theme/style.css/styleNN.css ..
we can discuss on this but ... as i said
Quote:
I hope i got the content of this discussion correct..
perhaps i should not drink and drive [my pc] late nights
but if u use Quote:
individual module-wise stylesheet files .. that .. needn't change the existing themes
why is the discussion to get that css match theme.css ??
Perhaps i should sleep a bit more .. michael
Re: Topic Options
Quote:
phpp wrote:
One of the reasons that new modules use individual module-wise stylesheet files is that it needn't change the existing themes, especially if a user has some themes and if he is not familiar with css. From a regular user's point of view, I think using the newbb.css is simplier than changing the theme/style.css/styleNN.css
This is true phppp, but on the flipside I think having this module level CSS causes more hassle/confusion than what it solves. It also depends on what you define as a "regular user" as many of the people I help with their XOOPS sites wouldn't know how to spell CSS, let alone know what it was or did. This is not to suggest that these people aren't smart, it's just that in my opinion a regular XOOPS user is not overly interested in the backend tech that makes the whole CMS tick, they just see it as a tool to manage their websites or intranets/extranets. Start adding complexity to this structure and they are just going to move onto a CMS that does what they wnat without having to hack the backend.
If NewBB 2 needs it's own CSS classes, then so be it. But I say lay the responsibilty of ensuring the NewBB 2 CSS classes are properly defined squarely on the theme designers. It just makes common sense to have 1 theme designer make the necessary changes to their themes rather than trying to field all the "how do I change the NewBB 2 drop down menu colours/size" style questions from potentially a few thousand people who are using the theme. There will be also some that don't even bother asking questions, and will just look for the next CMS.
What I think is more worrying is that we REALLY don't want to make module level CSS a trend for module developers. What happens if you end up with half a dozen modules all using their own CSS? You can't tell me that this will then be easier for the average XOOPS user to modify the CSS for each module of each theme they are using rather than just modifying it once in each themes CSS. As has been mentioned before, there is very good reason why there are themes, templates and modules. This is to keep a definite line in the sand between design, layout and code. By smudging these lines with module level CSS I really feel we are only going to hurt XOOPS in the long run, as the average XOOPS user is just going to look at using another CMS where they don't need to have the know how on how to modify code to get the result they are after.
All that said, I am no guru, and don't have the answers . Couldn't at least some of the NewBB CSS classes be redone to use the existing ones? I'd really love to help in anyway I can.
Re: Topic Options
i import newbb.css to style.css for all my themes ( i have 6 different color themes) and works fine but i have 2 qestions: 1- in theme directory what CSS file run last? i think style.css run after all name.css is there any way to run a name.css after style.css? 2- also is this possible to run a custom name.css in theme directory?
3-what is better? copy style code in module.css to style.css or simply copy module.css to theme directory
thanks in advance
Re: Topic Options
Thanks for checking my site phppp. I deleted the files through admin and regenerated them. It seems to work fine now except for the jumping menus and the colors but I can work that out later.
I'm still concerned about the six files that won't regenerate as I described in my earlier comment... Quote:
I followed this procedure. All but six files were regenerated. The six that weren't gave a message that the "selected file does not exist". But I confirmed that these files are indeed on the server. Here are the files: newbb_post.html newbb_preview.html newbb_quickreply.html newbb_block_active.html newbb_block_new.html newbb_block_top.html
Are those files not used in RC3? May I delete them from the server or will they be used in later versions of newbb2?
Re: Topic Options
The six files are not used any more. can be deleted.
Re: Topic Options
Good answer! Thanks.
Re: Topic Options
Quote:
If NewBB 2 needs it's own CSS classes, then so be it. But I say lay the responsibilty of ensuring the NewBB 2 CSS classes are properly defined squarely on the theme designers. It just makes common sense to have 1 theme designer make the necessary changes to their themes rather than trying to field all the "how do I change the NewBB 2 drop down menu colours/size" style questions from potentially a few thousand people who are using the theme.
From a developer's point of view, I totally agree with you that leave newbb's layout stuff (mainly newbb.css) to theme designers. And it is no problem for new themes to be designed. But how about existing themes? The NewBB Team would really appreciate if any theme designer could help update all the existing themes. However, it is not feasible right now.
Using newbb.css is perhaps just a temporary trad-off. What is the best solution? I have no idea.
Re: Topic Options
Quote:
Using newbb.css is perhaps just a temporary trad-off. What is the best solution? I have no idea.
Heres my take on the whole CSS issue. Aside from not including separate css on a module wide basis, something I agree 100% with brash on, if one MUST use css in their module, then it should be limited to class specific ID's that are alreay defined in the default style.css. Even this is sketchy, because many theme designesr create their own set of classes along with the standards as set out by XOOPS.
Who is going to guarantee compliancy? I expect no one. What happens when standard depreciate and the module developers is gone, leaving the end user behind. Just one more thing for people to have to fix on their own when a module drops off the edge of the delelopment planet, but is still widely used.
I for one will not be found modifying module wide css files. If I have 6, 7, 8 or more modules installed each with their own css, where am I supposed to find the time to edit all these if they don't conform to my theme and layout. This will kill users unable to edit css and will turn off future users.
Whats more, are module delelopers going to create one compliant style.css for their module, or are there going to be three css files in every module release? If I have just 6 modules installed, all with module specific CSS, thats 18 css files that I have to edit if one considers style.css, styleNN.css and MAC.css. What about people with 10 or modules installed. Lets say for the sake of argument, modules have developed to the point where they all include their own little bit of CSS. Do YOU seriously want to edit a possible 30 CSS files? It can and will happen if this is allowed to continue. I don't think this is going to appeal to a great amount of new users who are beginners. I myself don't mind editing it, but considering the time and dedication it takes, it's not worth it to me as more modules come out in this manner.
I appreciate the incredible amount of work gone into this module, but I seriously have to question what sort of example this will set for future developers. As it is, I am seriously turned off with editing my newbb .css for every theme change I make on the sites I'm working on. It adds to my test times and affect everything aspect of site management. I don't want to use the module for that fact alone, but it such a work of art, how can I not use it.
How about an option to use and choose between different ways the drop down is used and displayed. I don't know, I'm not a developer, I'm just a user just like everyone else, albeit with a little more experience the average beginner. Don't loose sight of that before you people flip off to me about what I'm saying, please. There has to be another way to simply the display of information currently in use. What that is, is way beyond my abilities to think.
As far as I'm concerned, I could do away with the colored drop down boxes. Why not use form data instead? Why does it have to be flashy with css? I agree, it looks awesome, but the hassle is not worth it to me personally and I think I speak for a great many people when I say that.
Another problem I have found, is that when I edit the module css to fit a theme, I switch themes only to see it looks like garbage and I have to edit it again. This is a PITA, plain and simple.
To sum up, either stick to currently used class definitions so that all we need to do is edit our style.css like we have for years, or drop the idea all together and reconsider something else. It's already proven to be a major hassle for beginners, and it's turning me off as along time user and strong supporter.
Re: Topic Options
Generally, my take on this is that module CSS should *only* deal with positioning, suiting the template(s) used in the module. Colouring should be avoided wherever possible, setting it to be transparent or inheried wherever this is feasible.
However, I do recognise that the standard classes in themes today (odd, even, head, foot, th) are quite possibly not enough. So let's hear from module devs and theme devs, what is needed and what those CSS classes should be called, so we can make a standard for XOOPS 2.1 covering these things.
Quite possibly, it would also make more sense to include the module CSS *before* the theme CSS, so themes can override module CSS.
Re: Topic Options
I probably agree here Mith, I think the number of available CSS classes that are available as standard are probably a bit on the lean side these days. I personally haven't had a lot to do with CSS outside of Xoops, so I don't know where to head from here. For those of you needing a bit of background to the origins of the standard CSS classes used in most themes, have a look at this document from the docs.xoops.org site. I'd be thinking we'd at least need a new class for drop down menu's. Doesn't NewBB have all the .com classes anyway, like the News module has the .item classes? maybe we need to also include a few more generic ones? I'm just guessing, and as it is early AM where I am and I haven't had my coffee yet, what I'm saying probably doesn't make a good deal of sense .
However, I'm still not sold on the use of module level CSS in any form. This is a biased view though because I can see some of the problems caused with cetain themes when this is done. For instance, with the current NewBB.css if you have a fixed width theme optimised for a screen reesolution width of 800 pixels, then you not only have to change the color, but you'll also need to alter font size and width settings to get the drop down menu's to display properly without blowing out your theme. It's for these kinds of reasons that I think it is a much beeter idea to expand on the exiting CSS classes in style.css than to start using module CSS.
For some reason your changes are not being written to the DB table specified, hence the error you see.
I think you may have to delete all your old icons first. I also think you "might" have to go into your DB and get rid of the reference to icon01.gif, but I can't confirm that.
Pred, or someone else may be able to field that one...
I get a blank page on all pages in administration menu (newbb options and so on ...)
So i can't set the permisions
And here is a error directly on the top of page ...
NewbbForumHandler::getForums error::SELECT forum_id, parent_forum, forum_name, forum_desc, forum_type, forum_moderator, cat_id, forum_posts, forum_topics FROM dev_bb_forums ORDER BY forum_order
Re: brash
@ brash
my replies to your two old questions
Q1. What if someone forgets to update the module once upgraded from RC2 to RC3? I'vent upgraded to RC3 yet. However, When i upgraded from Version 1 to RC2, all my forums were invisible when i forgot to update the module. Only the categories were visible.
Q2. regarding the SPAW editor. How it will look like in other browsers? I did enable the WYSIWYG editor in my Zmagazine module as well. However, in the admin panel, I wasn't getting the WYSIWYG editor interface when I used Firefox, but I was sure I had that way earlier. So later when I tried the same in IE, i got the WYSIWYG form. In firefox, it was the ordinary non-WYSIWYG interface!.. So yup, i believe in other browsers, it might be that way, and it is surely that way in Firefox
Re: NewBB 2.0 RC3 release
Thanks Stewdio, It works by replacing them all before install the xoops.
Folding subdirectories
Hi, all.
Please tell me how can I fold subdirectories in default? My start page is too long now....
Re: NewBB 2.0 RC3 release
I managed to download this main.php, but after updating the module I now have all newbb blocks double. I switched back to the old main file.
Re: NewBB 2.0 RC3 release
I get blank pages when I got to view a new thread. Plus the old threads that were there before the update do not have the Add Post option and when you view those threads they are blank pages as well.
Re: NewBB 2.0 RC3 release
When will the final version going to be release?
Re: NewBB 2.0 RC3 release -corrupted file
Quote:
MUST-DO: replace your /modules/system/admin/modulesadmin/main.php with the Bugfix
I just re-checked there is not any problem with that file.
Re: NewBB 2.0 RC3 release -corrupted file
Hmmmmmmmm... i downloaded it twice and its also the same.. can someone else try to download the file from the link and see if its corrupted?
Re: NewBB 2.0 RC3 release -corrupted file
Limecity I had exactly the same problem. I got a good download by right-click, save target as. Then The package opened fine.
Re: NewBB 2.0 RC3 release -corrupted file
same problem meaning the file is corrupted?
Re: NewBB 2.0 RC3 release -corrupted file
i seen this problem before but usually occured with opera browser, when it tries to download it doesn't download it as a file instead it outputs it to the screen or something..
i'm not seeing any problems when i downloaded it using IE 6 and firefox :S
Re: NewBB 2.0 RC3 release -corrupted file
i successfully download the file
sorry guys, its the crappy browser problem thanks mOnty ~
Re: NewBB 2.0 RC3 release
Is anyone else having the same problem I'm having... newbb2 rc3 notifications don't "stick"? I set my notifications to be emailed about any new post, but once I log out and come back, the notification is no longer selected. Tried it several times with different notifications options, same result.
Re: NewBB 2.0 RC3 release
Any idea for final release date yet or will there by an RC4 first?
Re: NewBB 2.0 RC3 release
if u checked out dev forge. i think there shudn't be any rc4. the finalpreview is been release. link
according to predator.. he said the final one will just be added documentation. Nothing change from the current FinalPreview package.
Re: NewBB 2.0 RC3 release
Hehe, as I keep going on about (sorry for the stuck-record impersonation) I just need the transfer script from Invision board XOOPS mod -> Newbb2.
If I had it I would transfer tonight
Re: NewBB 2.0 RC3 release
(comment deleted)
Re: NewBB 2.0 RC3 release
*i believe* final version has been released. but there's no announcement yet.