k, i'll look too, see if i can locate it

is it not in the language files?

i'd check the System module's language files, and also check the News module language files, and just search the file(s) for the exact phrase

i noticed the same thing on one of my XOOPS test sites... i was trying to use the news topic images that i have at my cs map site, yet they were too large for any news post that were less than a paragraph, lol

is the image's size not being defined by XOOPS or the themes? that could be why the layout isn't compensating (but i dunno, i'm no html buff)

if i were you, i would go ahead and install XOOPS somewhere, and start slowly migrating, and then just copy over your WF-Sections sql table when you DO migrate fully

that way, you'll be able to become familiar with XOOPS and setting up html documents in WF-Sections, and you'll maybe be able to knock out a large amount of the work easily

you can edit the theme directly with Dreamweaver, since the theme design is contained in an html or xml file usually (from what i've seen)

for converting all your html content, i would just get WF-Sections (i put out a version today that slightly enhances Catzwolf's version, it's in the Modules forums), put all your html files in the WF-Sections html folder, then go into WF-Sections admin to assign each html file to an article title (along with whatever other settings you want)

you can edit the html by opening it all up in Dreamweaver or wherever else and do a mass find-replace for all image urls (assuming that your image urls were usually similar), and change them to

what i did, is i put my images into an image folder, then put the folder inside the html folder... so now it's "html/htmlimages/imagename.jpg" for me...


as for fixing the other links, try to find ways to mass find-replace those urls as well... probably best to again, use dreamweaver (or Editplus2)

hopefully that suggestion helps ya
btw, for all your html files, if you have headers/footers, i would suggest getting rid of them, so the file fits in with your new XOOPS site better

i tried XOOPS before i went with phpnuke... from what i've seen, there have been alot of improvements from when i first tried it, cus i didn't like it the first time

so maybe it's better that you waited until now

i've been a phpnuke user since february of this year, and for awhile there, i was pretty involved in the community, and i stuck with it, since i had not found anything better

phpnuke has a HUGE community, but the problem is, there are so many splits in the community... the lead developer (Francisco Burzi) has a tendency to screw over the community (the details of which i'm not going to go into, it's a long history..), and until more recently, there was no 'dev team', it was just the one official developer that didn't support phpnuke, put out a buggy product filled with security holes, etc etc

the reason why phpnuke has such a big community though, is because of how *easy* it is to modify or hack the code... which also causes problems, since then many of the addons that you find, totally alter the core nuke code, which means that every release you want to upgrade to will overwrite any changes that have been made, and your 'addons' no longer work

nukecops.com has fast risen as the 'support' site for the community, and they became so big, nukecops.com started to dwarf phpnuke.org, at which point Francisco allowed nukecops.com (the staff/developers) to become the official dev team (but their code submissions are still implemented at a slow rate by FB, for some unknown reason)

it's a troubled community, tons of people argue about GPL, licensing, argue and fight about Francisco Burzi, some support NukeCops.com, others support NukeScripts.net, etc etc..


i've gotten tired of the bs, the bugs, the security issues, so all new sites that i release will be built using Xoops2. the XOOPS CMS is the easiest that i've ever used, the most bug-free CMS i've ever seen, and from what i can tell, is very secure... it has a great community and very helpful developers that are actually committed to the product

there are rarely GPL arguments from what i've seen, everything is much nicer here.

I will be moving my existing phpnuke sites to Xoops, once a few modules that i need are converted to Xoops

btw, these are my nuke sites:http://www.csmapcentral.comhttp://www.nukebbmods.net <<
and i have a XOOPS site in development:http://webhostingparadise.com << (site is currently shut down to anyone that's not me, lol, while i work on it)

i hope i helped you some. btw, if you absolutely must go the *nuke way, i would suggest watchinghttp://www.nsnnuke.org << it's a branch from PHP-Nuke with many code rewrites and security fixes, it's still in beta phase, but i'll bet $$ that it'll be bigger and better than php-nuke, and it might even give XOOPS a run for it's money...

nsnnuke isn't ready for production sites yet, but XOOPS is, so i'm sticking with XOOPS

as i mentioned in this thread:
https://xoops.org/modules/newbb/viewtopic.php?topic_id=14308&forum=4

i fixed the email bug and corrected/created several language definitions


then i noticed that above and below the Category index listings, are phrases referring to 'test header' and 'test footer'

so, went through the config file, and added in these following options (the sql was already there, but options to modify the sql were non-existent):

changes:
--------
--Added configuration option for Category Heading
--Added configuration option for Category Header
--Added configuration option for Category Footer
--------

you can get the new package here:
WF-Sections v1.01b

laf, i never password protect my files, so it's operator error or your unzip proggie can't handle it

btw, no 'update' needs to be run, there were no changes to templates or sql