FWIW:

I just stuck the hard coded url version onto a XOOPS site and it didn't show up either. But I'm using Opera Browser.

So I swapped over to MSIE and hey presto it worked on the live site.

Hope that get's you started on a lead somewhere.

That code I posted (with hard coded url) brings up your scanning lighthouse movie just fine when I paste it into my html editor.

That may have been a typo by astonstreet but there should be no dir slash after <{$xoops_imageurl}>

It should read

<{$xoops_imageurl}>logo.swf

If that doesn't work then your browser or your server or your ISP is blocking that content type. Which is probably unlikely.

Try this:

<object classid="clsid27CDB6E-AE6D-11cf-96B8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,42,0"
id="logo" width="530" height="80">
<param name="movie" value="http://www.warpigw2.com/themes/fc_clan_blue/logo.swf">
<param name="bgcolor" value="#000000">
<param name="quality" value="high">
<param name="allowscriptaccess" value="samedomain">
<embed type="application/x-shockwave-flash"
pluginspage="http://www.macromedia.com/go/getflashplayer"
width="530" height="80"swLiveConnect="true" allowScriptAccess="samedomain"
></embed>
</object>

No you can't install this module twice. But some people have gotten around this by creating a duplicate module:

See News2 - News Module Clone

Wilkinsa,

1.
Take another look at your modules. The xoopsblock code is trying to create content in which a class is called that doesn't exist. The tabview class must be from a custom module (non XOOPS core).

Disable all your modules until you find the offending module or do text search through the source code and look for "tabview".

2.
Also, in the error message, the path is quoted as

/home/jeffsqs/public_html/class/

which means the root dir of the XOOPS installation is

/home/jeffsqs/public_html

if this is correct this should be the fully qualified path to the XOOPS files from '/'.

Venezia

The class tabview must have come from one of the installed modules. Sounds like some of the files are missing for that module or file permission problem.

What modules are installed?

Xoops system is looking for the file called "adminmenu.php". It should exist here:

<-path to your installation->/cache/adminmenu.php

You do not need to create this file. XOOPS creates it. But XOOPS needs to have correct privileges in cache folder to do this.

Make sure you are the owner the cache folder and that it's permissions are set to 777. If this is correct, XOOPS will create the adminmenu.php file when you press the "first time" button and you shouldn't see the message again.

Venezia

The sytle for this is defined in the default theme stylesheet.

Find the file

name_of_your_xoops_dir/themes/default/style.css

Find the line

th {background-color: #2F5376; color: #FFFFFF; padding : 2px; vertical-align : middle; font-family: Verdana, Arial, Helvetica, sans-serif;}

This is the style definition for table headers. You can change the values to anything you like.

Don't forget to make the same changes to the other browser stylesheets in this theme: styleMAC.css, styleNN.css

Have a look at the zip or tar file for the patch. It only includes common.php and version.php.

From the changes.txt document following changes are missing:


2004/08/21: Version 2.0.7.1

Fixed bug #1006511 about $xoops_isadmin misuse (skalpa/the www.xoopscube.jp community):
- Changed XoopsUser::isAdmin() behavior to prevent problems with modules that misuse this function
- Fixed permission checking in user profile page, to only show admin links to people who are supposed to see them
- Fixed permission checking in the comments system, to only show admin links to people who are supposed to see them
Fixed incorrect escaping of configuration values in 2.0.7 (skalpa)
Changed db proxy class error message from "Action not allowed" to "Database update not allowed during a GET request" (skalpa)
Fixed bug #964084: if comment title is long multi-byte character.last byte loss (Mithrandir/domifara)
Fixed bug #977360: Wrong icon in comment bloc (Mithrandir/zoullou)
Fixed bug #976534: modules incompatibilities in 2.0.7 (Mithrandir/gijoe_peak)
Fixed bug #975803: Typo in class/pagenav.php (Mithrandir/Dave_l)
Fixed bug #974655: slogan variable with XOOPS 2.0.7 (Mithrandir/brashquido)
Fixed bug #987171: typo in edituser.php (Mithrandir)
Applied patch #928503: Search results for modules with granted permissions optimised (Mithrandir/malanciault)
Applied patch #988715: cp_header.php language (Mithrandir/phppp)
Fixed MyTextSanitizer PHP notices (Mithrandir)
Fixed XoopsForm PHP Notices about an unset _extra property (Mithrandir)

Is there a package to do a manual update from 2.0.7 to 2.0.7.3?

I see there is a 2.0.7.x to 2.0.7.3 patch, but does that also catch the changes between 2.0.7 and 2.0.7.1? There seems to be a lot of changes in the changes.txt document but the only files included in the zip are common.php and version.php.

Venezia