Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Search

 
Advanced search

8043 Posts in 1856 Topics- by 2099 Members - Latest Member: roi
Calendar Script CommunityEverything ElseGeneral Use (Moderators: scott, DanO, Marty)Perl name conflict (Config) vs. CGI::SSI how to resolve?
Pages: [1]   Go Down
Print
Author Topic: Perl name conflict (Config) vs. CGI::SSI how to resolve?  (Read 282 times)
0 Members and 1 Guest are viewing this topic.
Zim
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« on: March 19, 2004, 03:17:00 PM »

Ok, in an area of Perl that I don't know well.

I am trying to add header/footer material around the calendar using CGI::SSI to call some php files.

But I'm getting a conflict between the variable "Config" defined in calendarscript and there must be one in CGI::SSI.

I get the error message:
 

quote:
ERROR PROCESSING TEMPLATE
There was an error in your template file. Below is the template file and also the perl code generated from it to help you with debugging.

Global symbol "%Config" requires explicit package name at /System/Library/Perl/5.8.1/Time/Local.pm line 27. BEGIN not safe after errors--compilation aborted at /System/Library/Perl/5.8.1/Time/Local.pm line 38. Compilation failed in require at /Library/Perl/5.8.1/Date/Format.pm line 47. BEGIN failed--compilation aborted at /Library/Perl/5.8.1/Date/Format.pm line 47. Compilation failed in require at /Library/Perl/5.8.1/CGI/SSI.pm line 9. BEGIN failed--compilation aborted at /Library/Perl/5.8.1/CGI/SSI.pm line 9. Compilation failed in require at rjcheader.pl line 3. BEGIN failed--compilation aborted at rjcheader.pl line 3. Compilation failed in require at (eval 1) line 56.


How do I make them play nicely together?  I have tried replacing the references in the template to Config with main::Config, but that was not enough (and where my Perl knowledge ran out)

Thanks,
Mike

[This message has been edited by Zim (edited March 19, 2004).]

[This message has been edited by Zim (edited March 19, 2004).]

Logged
Zim
New Member
*

Karma: 0
Offline Offline

Posts: 0


WWW
« Reply #1 on: March 20, 2004, 10:26:00 PM »

My problem appears to be solved.

Seems I stumbled on a bug that Matt fixed in 3.1.. when I did the 3.21 upgrade, I moved the new files in by hand.. leaving the previous Config.pm file in place.  So when I finally installed a competing module, it only now showed up.  Removal of the old Config.pm file (no longer needed by CS) seems to have solved the problem.  (thanks to Conundrum over at devshed for helping me solve this)

Mike

------------------

Logged
Pages: [1]   Go Up
Print
Jump to: