[Bug 6317] New: access the url above and try to access the event, it will give an errror.

http://bugs.xaraya.com/show_bug.cgi?id=6317

           Summary: access the url above and try to access the event, it
                    will give an errror.
           Product: App - Core
           Version: Weekly Tarball
          Platform: All
               URL: http://isaca.dolari.info/index.php?module=julian&func=da
                    y&cal_date=20090209
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P3 - Standard
         Component: Modules
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
AppleWebKit/528.7 (KHTML, like Gecko) Chrome/1.0.155.0 Safari/528.7
Build Identifier: 

Error Message

SYSTEM ERROR
PHP: ERROR NOTICE
At: ......../modules/julian/xaruser/viewevent.php (Line: 178) Undefined index:
eCalendarID

EXPLANATION:
There is an error in the PHP code that is being processed.

Reproducible: Always

Steps to Reproduce:
1. go
http://isaca.dolari.info/index.php?module=julian&func=day&cal_date=20090209
2. click on the only event available there
3. similar error appeared also when i tried to insert the event, however the
event appears to be at least partialy registered in julian.
Actual Results:  
Error Message

SYSTEM ERROR
PHP: ERROR NOTICE
At: ......../modules/julian/xaruser/viewevent.php (Line: 178) Undefined index:
eCalendarID

EXPLANATION:
There is an error in the PHP code that is being processed.

Expected Results:  
the details of the event.

let me know if you need access to the system, the instalation is pretty default
right now, not a lot of customizations done.


-- 
Configure bugmail: http://bugs.xaraya.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

---- ** IMPORTANT ** READ BELOW ** ----
[Clip Me Start]
--------------------------------------------------------------------------
If you wish, you can reply to this message directly **however**, make sure
to use the "Reply To All" feature of your client **and** ensure that the 
bug specifier is in the subject (ie: [Bug ####]). Also, you _MUST_ have 
you're From or Reply-To address set to the same address you use to log
into your bugzilla account or your reply will not be attached to the bug.
--------------------------------------------------------------------------
[Clip Me End]