233692
You did not say whether you have a backup`? Are you doing all this on your live site?
Do i understand right that the old version of WF-Sections was working fine and then at some point stopped working or was it never really working?
You could deactivate (NOT UNINSTALL) all other modules except WF-Sections and see if the problem is still there. If it is not ... activate one after another and see which one might interfere.
You could go back to the old version of WF-Sections to see what the original error message there was. This actual one could be caused by the different database tables.
Well i think it would be nice to do this testing on a local setup (using XSAS or something like that) which would also show if this only happens on the webserver or also on your local system. (different Apache, PHP ,...)
Do i understand right that the old version of WF-Sections was working fine and then at some point stopped working or was it never really working?
You could deactivate (NOT UNINSTALL) all other modules except WF-Sections and see if the problem is still there. If it is not ... activate one after another and see which one might interfere.
You could go back to the old version of WF-Sections to see what the original error message there was. This actual one could be caused by the different database tables.
Well i think it would be nice to do this testing on a local setup (using XSAS or something like that) which would also show if this only happens on the webserver or also on your local system. (different Apache, PHP ,...)
233693
only one db connection is made per page request, which is enforced by the XoopsDatabaseFactory::getDatabaseConnection(); function. The global $xoopsDB object is generated via this function (see /include/common.php).
233694
The problem is, their is no update script yet, you can't deactivate, but need to uninstall and reinstall, sorry, the new tables in the new version can only be changed this way at the moment till the update script is released
The error message is not a problem
The error message is not a problem
233695
Parse error: parse error, unexpected T_CLONE, expecting
T_STRING in /opt/lampp/htdocs/xampp/iiss/kernel/object.php on
line 504
------
function &clone()
{
$class = get_class($this);
$clone = new $class();
foreach ($this->vars as $k => $v)
{
$clone->assignVar($k, $v['value']);
}
//need this to notify the handler class that this is a newly created
object
$clone->setNew();
return $clone;
}
-------
Server:
Apache, PHP5, Linux
What's wrong ?
T_STRING in /opt/lampp/htdocs/xampp/iiss/kernel/object.php on
line 504
------
function &clone()
{
$class = get_class($this);
$clone = new $class();
foreach ($this->vars as $k => $v)
{
$clone->assignVar($k, $v['value']);
}
//need this to notify the handler class that this is a newly created
object
$clone->setNew();
return $clone;
}
-------
Server:
Apache, PHP5, Linux
What's wrong ?
233696
Hello Bender..
The new wf-sections is not a problem since this problem existed even before i updated to it. I did that because i though it might solve the problem since i knew that wf-sections 2 was buggy and also i thought it might have been a coruption problem. So i wanted to kill those two possibilities by simply updating to a new version.
I deactivated the old module, replaced the old files and then updated and reactivated the module. The content is there, it's not lost as i see it in the admin section, the article pages don't display only, that's the whole problem.
It may not even have a direct connection with wf-section but with XOOPS as problem existed with the old version also, and now with the new, idenpendantly.
Does this debug output means anything:
Thank you
Daniel
EDIT: Sorry for the double post, an accident.
The new wf-sections is not a problem since this problem existed even before i updated to it. I did that because i though it might solve the problem since i knew that wf-sections 2 was buggy and also i thought it might have been a coruption problem. So i wanted to kill those two possibilities by simply updating to a new version.
I deactivated the old module, replaced the old files and then updated and reactivated the module. The content is there, it's not lost as i see it in the admin section, the article pages don't display only, that's the whole problem.
It may not even have a direct connection with wf-section but with XOOPS as problem existed with the old version also, and now with the new, idenpendantly.
Does this debug output means anything:
Notice [PHP]: Undefined index: articlepage in file modules/wfsection/article.php line 68
Thank you
Daniel
EDIT: Sorry for the double post, an accident.
233697
Hello Bender..
The new wf-sections is not a problem since this problem existed even before i updated to it. I did that because i though it might solve the problem since i knew that wf-sections 2 was buggy and also i thought it might have been a coruption problem. So i wanted to kill those two possibilities by simply updating to a new version.
I deactivated the old module, replaced the old files and then updated and reactivated the module. The content is there, it's not lost as i see it in the admin section, the article pages don't display only, that's the whole problem.
It may not even have a direct connection with wf-section but with XOOPS as problem existed with the old version also, and now with the new, idenpendantly.
Does this debug output means anything:
The new wf-sections is not a problem since this problem existed even before i updated to it. I did that because i though it might solve the problem since i knew that wf-sections 2 was buggy and also i thought it might have been a coruption problem. So i wanted to kill those two possibilities by simply updating to a new version.
I deactivated the old module, replaced the old files and then updated and reactivated the module. The content is there, it's not lost as i see it in the admin section, the article pages don't display only, that's the whole problem.
It may not even have a direct connection with wf-section but with XOOPS as problem existed with the old version also, and now with the new, idenpendantly.
Does this debug output means anything:
Notice [PHP]: Undefined index: articlepage in file modules/wfsection/article.php line 68
233698
Ok good news, so I want to make a compatibility list.
There is the tested browsers, perhaps other versions can be comptabile.
(Mozilla since ver 1.3 would be comp.)
TESTED BROWSERS
Windows
-Internet Explorer 5.5, 6, 6sp1, 6sp2
-Mozilla 1.7,1.8
-Firefox 0.8, 0.9, 0.93, 1.0pre
-Netscape 7.1, 7.2
MacOs:
-Mozilla 1.31 (wamcom-Version)
MacOsX:
Mozilla 1.5 (problems with dialogs)
Linux:
-Mozilla 1.7, 1.7.2
NON COMPATIBLE BROWSERS
Windows:
-Opera
-Mozilla 1.2 or lower
MacOs:
-Safari.
-Internet Explorer 5.17
-Mozilla 1.2 or lower
MacOsX:
-Safari
-Internet Explorer 5.23
Linux:
-Konkeror
-Mozilla 1.2 or lower
There is the tested browsers, perhaps other versions can be comptabile.
(Mozilla since ver 1.3 would be comp.)
TESTED BROWSERS
Windows
-Internet Explorer 5.5, 6, 6sp1, 6sp2
-Mozilla 1.7,1.8
-Firefox 0.8, 0.9, 0.93, 1.0pre
-Netscape 7.1, 7.2
MacOs:
-Mozilla 1.31 (wamcom-Version)
MacOsX:
Mozilla 1.5 (problems with dialogs)
Linux:
-Mozilla 1.7, 1.7.2
NON COMPATIBLE BROWSERS
Windows:
-Opera
-Mozilla 1.2 or lower
MacOs:
-Safari.
-Internet Explorer 5.17
-Mozilla 1.2 or lower
MacOsX:
-Safari
-Internet Explorer 5.23
Linux:
-Konkeror
-Mozilla 1.2 or lower
233699
Xoops has a wide variety of good content modules not included with the installation to allow users to choose their own preferences
see "xoops for dummies" and the content section, some content modules listed there.
The big brother of all content modules is wfsection
http://www.wf-projects.com/
see "xoops for dummies" and the content section, some content modules listed there.
The big brother of all content modules is wfsection
http://www.wf-projects.com/
233700
it's postfort making something to read. it's not the best test i've seen, but it's the same for all CMS : basic install with basic theme.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|