XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Modules Support forums / 
  3. Module troubleshooting 
  4.  / extCal problem in 2.4.2
Register
1
barryc
extCal problem in 2.4.2

  • 2009/12/23 14:39

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


I recently upgraded to XOOPS 2.4.2 and now realize that this has broken the extCal module. When trying to access the admin pages I get a white screen. Debug reports:

Quote:
Fatal error: Cannot redeclare adminmenu() (previously declared in /home1/barrycne/public_html/aka/modules/extcal/admin/function.php:3) in /home1/barrycne/public_html/aka/modules/xoopsinfo/include/functions.php on line 96

None All Errors (1) Queries (17) Blocks (0) Extra (2) Timers(5)

Errors

Notice: Constant _DB_POSLINE_DESC already defined in file /modules/backup/language/english/modinfo.php line 24


Has anyone else seen this problem and/or have a solution? I will also post to zoullou's site.

[Edit] Just looked on zoullou's site and found reference to similar problems but no fixes. I might have to change calendars. That would be a shame. This is supposed to be a core problem so I'm going to post to the 2.4.2 forum as well.

barryc
2
ghia
Re: extCal problem in 2.4.2

  • 2009/12/23 15:44

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Did you try the default admin theme?
If that works better, try once the new version of Oxygen.
3
Anonymous
Re: extCal problem in 2.4.2

  • 2009/12/23 17:20

  • Anonymous

  • Posts: 0

  • Since:


I haven't been able to access to module's admin index page since ExtCal version 2.2.x was released, both on XOOPS 2.4.2 and earlier versions (certainly since XOOPS 2.3.x and possibly since 2.0.x - bad memory!).

I can access the module's other admin pages though.

I haven't used the module in anger since upgrading to XOOPS 2.4.2 other than to edit existing events; this seems to work okay.

As for alternatives, GIJoe has a module that might work on XOOPS 2.4.2 - google for "peak xoops" and you'll find his site.

[edit]just re-read your post:

[QUOTE]Notice: Constant _DB_POSLINE_DESC already defined in file /modules/backup/language/english/modinfo.php line 24[/QUOTE]

What is this /backup/ sub-folder in your modules directory? If it is a module then what happens if you deactivate it?[/edit]
4
barryc
Re: extCal problem in 2.4.2

  • 2009/12/23 17:30

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Quote:

ghia wrote:
Did you try the default admin theme?
If that works better, try once the new version of Oxygen.


Hi ghia,

I had not thought to try a different admin theme and indeed I was using Oxygen. I switched to the default admin theme and I can again see the extcal admin pages. So, I downloaded the new oxygen theme from Sourceforge and installed it, after backing up the old oxygen files. The problem in accessing the extcal admin pages still exists. I get the same white page and same error message.

There seem to be some problems with extcal under 2.4.2. You can see some comments about it on zoullou's site. My investigation started after a member on my site complained that he could not post an event. I can post events as admin but haven't yet tested it when logged on as a non-admin. I'll do that soon and report back.

For now, the oxygen admin theme breaks extcal.

barryc
5
ghia
Re: extCal problem in 2.4.2

  • 2009/12/23 17:35

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


So, in the default admin GUI, it works alright/

The Oxygen interface has some problems with admin menus and when using some module combinations as ExtCal, News and the Backup module, their admin menus can get mixed up and throwing white pages.
6
barryc
Re: extCal problem in 2.4.2

  • 2009/12/23 17:39

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Yes, it works fine with the default admin theme.

As posted by JAVesey, the error message mentions the backup module and I was curious about that too but haven't yet had a chance to try inactivating it. I actually don't use it now so could try that. I do my db and file backups manually.

Will report back.

barryc
7
barryc
Re: extCal problem in 2.4.2

  • 2009/12/23 18:02

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


More testing:

I did test the ability to post as a registered user (non-admin) and it worked OK. That was done while the default admin theme was active. I did not try to post under the oxygen theme. I will have to get back to my complaining user to follow up on that.

I also inactivated the backup module then switched to oxygen again. It is still broken. This is a real problem that will have to be addressed for that theme. I really like the Oxygen admin theme but won't be able to use it until these problems are solved.

barryc
8
trabis
Re: extCal problem in 2.4.2

  • 2009/12/23 20:05

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


There is no problem with oxygen/core. Problem is on module side.
Oxygen loads every modules menus, if modules are using same function names then we have a collision. Solution is prefixing modules functions with the modules dirname, for example xoopsinfo_adminMenu() and extcal_adminMenu().

According to Xoops Coding Standards:
Quote:

Overall Proposal

1. Names for all classes and functions inside XOOPS should start with Xoops;
1. First letter for function names should always be in lowercase; in case necessary names should be separated using underscores "_" not camelCaps:
* core functions should be started with xoops_
* framework and library functions should be started with xoops_[framework or library identifier]_
2. Class names should always be separated using camelCaps, which is addressed below;
2. Names for shared variables generated by XOOPS should start with $xoops following camelCaps style
* Private (or not shared) variables are encouraged to follow the style as well
3. Third-party applications, including modules, should not start with Xoops_ but start with corresponding identifier
* Module class names should start with [module identifer, usually directory name] following camelCaps style, e.g. NewbbPost
* Module function names should start with [module identifer, usually directory name]_, e.g. newbb_getPostCount()
* Module variables should start with $[module identifier], e.g. $newbbPostCount

9
barryc
Re: extCal problem in 2.4.2

  • 2009/12/24 1:04

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Trabis suggested a fix to make the admin menu in extcal unique, allowing it to be accessed under the oxygen admin theme. See this thread.

barryc
10
ghia
Re: extCal problem in 2.4.2

  • 2009/12/24 1:37

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


This was and still is not a problem in the other GUI's.
It is up to the Oxygen GUI, to correct its own incompatibility with the usual programming style of modules. Altough not according to the strict rules, it has become a defacto standard.

If it can not be done, then the Oxygen should not be promoted further or instated as standard admin GUI.

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

200 user(s) are online (143 user(s) are browsing Support Forums)

Members: 0

Guests: 200

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits