Re: XOOPS 2.3.3 Final Issues
  • 2009/4/14 16:06

  • Gordon

  • Just popping in

  • Posts: 4

  • Since: 2009/3/26

Thanks JAVesey!

I have installed the PROFILE!
That is why i do not see the image Captcha?

Re: XOOPS 2.3.3 Final Issues
  • 2009/4/14 16:09

  • Anonymous

  • Posts: 0

  • Since:

Gordon wrote:

That is why i do not see the image Captcha?

No, your site's users should see the captcha image on page 2 of the registration process when the profile module is not installed.

But if you are happy......

Re: XOOPS 2.3.3 Final Issues
  • 2009/4/14 16:41

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1

If the image (with the letters and digits to type over) is not showing, check the required directory and switch caching off for modules system and profile.

Re: XOOPS 2.3.3 Final Issues
  • 2009/4/26 20:18

  • fathershand

  • Just popping in

  • Posts: 6

  • Since: 2009/4/15

I have recently installed 2.3.3 and am getting the following error in server error log. Is there a bug?

[Sun Apr 26 06:28:25 2009] [error] [client some.ip] File does not exist: /var/www/vhosts/blahblah/httpdocs/x/htdocs/jseffects

There is no jseffects directory. Why?

Re: XOOPS 2.3.3 Final Issues
  • 2009/4/29 0:17

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1

You are probably using some relative URL's to it, which no longer corresponds, when used in a block.
Add the XOOPS_URL to it.

Re: XOOPS 2.3.3 Final Issues - images, styling
  • 2009/5/12 2:09

  • jph000

  • Just popping in

  • Posts: 60

  • Since: 2004/8/2 2

On a demo server, I upgraded XOOPS from 2.3.2b to 2.3.3. The 2.3.2b-to-2.3.3 upgrade package included the System module, which was updated; and the pm and profile modules (which remained inactive). Upgrade instructiions included in the release_notes file were followed.

Then I spent much more time than expected (the entire afternoon!) figuring out why the site looked different and why the header image was missing. Well, the upgrade package was missing some files in themes/default folder:


which were in the full release. But despite that location, the code was looking for the xoops-logo.png at the root level; so, I copied it there and the header looked okay at last.

Favicon use had changed to the themes/default/icons/favicon.png file, and so had overridden the favicon at the root level.

I also found no mention that the default theme had been dramatically changed. In particular, the typography was redesigned in the themes/default/style.css file, along with additional styling: the font sizing scheme in em's versus %'s, color scheme, and a large new section for the system_siteclosed page, which was part of the new themes/default/modules/suystem folder.

Validator Bugs


$ret .= '<div id="xo-pagenav">';

Changed to

$ret .= '<div class="xo-pagenav">';


#xo-pagenav {

#xo-pagenav a {

#xo-pagenav a:hover {

Changed to

.xo-pagenav {

.xo-pagenav a {

.xo-pagenav a:hover {

Re: XOOPS 2.3.3 Final Issues
  • 2009/5/29 15:08

  • edudelta

  • Just popping in

  • Posts: 12

  • Since: 2009/3/18

But the 'thank you for your submission' page losts its style and displays left aligned with a black background. i report too.

and the page for Site Closed is with a similar problem.
The page don´t is translated and no styles.


Who's Online

179 user(s) are online (140 user(s) are browsing Support Forums)

Members: 0

Guests: 179



Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits