After upgrading to XOOPS 2.0.10 Beta 3 I noticed my custom block not showing.

After several hours debugging my css, html, tables, etc. I finally tracked it down to mainfile.php (i overwrote it with the 2.0.92 mainfile.php and the block returned).

Sifting through mainfile.php I see that system_dummy_block.html is the file that allows for custom block content.

My guess is that something broke with this feature between 2.0.92 and 2.0.10 Beta 3.

The best way to verify this is to add a new block and use "{X_SITEURL}" for the content (or anything really). Set the block to visible and see if it shows up.

Hopefully this is the right place to post this bug as I'd love to find a solution.

Thanks much!

i've found the link and was just on my over to post it here :)

https://xoops.org/modules/newbb/viewtopic.php?topic_id=34227&start=0

ironically, it's the forums I was thinking of leaving out.

reviews and articles are the real beast.

if this handles moving members over though that would would be great - although script is for a phpbb conversion not a nuked phpbb conversion which has several other layers.

certainly is a good start though.

Quote:

glad you find the links helpful they've been a great resource for me.

once you start creating your own theme XOOPS will use your theme's stylesheet. in that stylesheet you can set your font sizes. alternately, you can modify the existing XOOPS CSS files to use em instead of points or pixels.

for em font sizes try the following: font-size:0.95em;
This is similar to: 11px/8pt

I've seen the post over at:https://xoops.org/modules/newbb/viewtopic.php?topic_id=31111&forum=27&post_id=148947

Are there any conversion scripts out in the wild? I'm looking to convert a fairly large phpnuke site to XOOPS and consider it a daunting task.

priorities would be: members, articles, and reviews. im deliberating dropping forum support altogether.

thanks for the help...

Looks like this thread exists in two places but this is the more happenin' of them so I will repost here :)

An article was published recently on the topic of Innovative Design and Accessibility:http://www.digital-web.com/articles/innovative_design_accessibility/

The article doesn't address CMS or XOOPS for that matter but it's a worthy read nonethless.

Here are some other links on the topic:

Building Accessible Web Sites in Seven Steps
http://www.techsoup.org/howto/articlepage.cfm?ArticleId=381&topicid=13&cg=content&sg=feature

W3C Accessibility Quicktips Reference Guide
http://www.w3.org/WAI/References/QuickTips/

Web Content Accessibility Guidelines 1.0
http://www.w3.org/TR/WCAG/

5 First Steps for Designing Accessible Web Sites
http://www.ataccess.org/rresources/web/5firststeps.html

Accessibility Best practices
http://www.spingroup.com/htmdocs/resources/article.php?parent=5&catcode=57

The Sound of the Accessible Title Tag Separator
http://www.standards-schmandards.com/index.php?2004/11/06/6-the-sound-of-the-accessible-title-tag-separator


With regards to the creation of several user-selectable style sheets to enable font sizing - this is not necessary. With the use of em (instead of pt or px font sizes) the user can modify the font size with the browser function.

I'm currently redesigning my site (moving from phpnuke to xoops) and I can safely say that the templates themselves *can* be built for accessibility (using XHTML and CSS) with some decent hacking. Content may be another beast but the template is always the first step.

An article was published recently on the topic of Innovative Design and Accessibility:http://www.digital-web.com/articles/innovative_design_accessibility/

The article doesn't address CMS or XOOPS for that matter but it's a worthy read nonethless.

Here are some other links on the topic:

Building Accessible Web Sites in Seven Steps
http://www.techsoup.org/howto/articlepage.cfm?ArticleId=381&topicid=13&cg=content&sg=feature

W3C Accessibility Quicktips Reference Guide
http://www.w3.org/WAI/References/QuickTips/

Web Content Accessibility Guidelines 1.0
http://www.w3.org/TR/WCAG/

5 First Steps for Designing Accessible Web Sites
http://www.ataccess.org/rresources/web/5firststeps.html

Accessibility Best practices
http://www.spingroup.com/htmdocs/resources/article.php?parent=5&catcode=57

The Sound of the Accessible Title Tag Separator
http://www.standards-schmandards.com/index.php?2004/11/06/6-the-sound-of-the-accessible-title-tag-separator


With regards to the creation of several user-selectable style sheets to enable font sizing - this is not necessary. With the use of em (instead of pt or px font sizes) the user can modify the font size with the browser function.

I'm currently redesigning my site (moving from phpnuke to xoops) and I can safely say that the templates themselves *can* be built to for accessibility with some decent hacking. Content may be another beast but the template is always the first step.

Quote:

Getting hacked through phpbb and moving to XOOPS with your phpbb board intact will not solve the problem. Several security patches have been released recently for phpbb - you should consider patching your installation first before trying to move it into another phpbb fork.