hey everyone,

I got no response from my previous query so I am rewording it and putting it out again, I just don't believe i am the only one with the same issues!

Here are the relevant settings in my preference settings:

xoops server timezone: GMT -6 (florida - where my webhost is)
Xoops default timezone: GMT +10 (australia - where I am)
PiCal timezone of the server: value of the Xoops config

I have tried a swag of different settings: eg, changing xoops server to +10 to reflect fact I'm in OZ changing piCal settings to reflect daylight savings, etc.

When piCal imports my icalendar data, it still changes the times I have events listed as.

This is what piCal has listed in my table maintenance page:
Timezone of the server (winter): -6.0
Timezone of the server (summer): -5.0
Zonename of the server: CDT
The value of XOOPS config: +10.0
The value of piCal using: -6.0

I am confused and getting a little tired of playing with this.

Please help, I think this is the best product for what I want, but I am getting no joy and may need to start looking around for something different.

Thanks,

Jon

You missed the necessary informations.

- Paste a VEVENT in the ics file.
- Write the displaying time of the event imported from the VEVENT.

And I don't support via e-mail at all.
Don't send GIVEME or HELPME mails to me, please.

And don't behave impolitely.

There are no reasons I have to support impolite men like you.

I would like to apologise to you GiJoe and whom ever else was offended by my language!

I was getting increasingly frustrated at trying to resolve the issue and was getting no where and when I turned to the board I became more frustrated at my problem as I couldn't understand why any of the clever people her could help.

Thanking you for helping me out GiJoe! Mind you I haven't a clue what a VEVENT is but I will look it up and see if I can work it out. Being new to PHP and Xoops all at the same time has given me a steep learning curve, but I would accept any advice and help anyone is willing to give!

Please Note
I determined my GMT problem is not with the distributed piCal. I tried to force timezone in the entry form to be GMT-6 without the popup, and somewhere in the process things got messed up.

I replaced the original piCal.php class file and the GMT situation is correct again.

Sorry for any inconvenience in my posting here.
Paul

old message follows:

Hi there,

piCal is awesome.

I am also having a problem with time.
It all seems to stem from the Timezone situation.

Timezone of events I put in: -6
Timezone of xoops, and server, etc.: -6

When I put events in, they get placed on the calendar according to GMT, rather than according to GMT-6.

I can read the details of the event, and it shows of course the GMT time (which is how it seems to be placing the event on the calendar) and the actual time that I submitted the event with (which is GMT-6.)

Any ideas on this would be greatly appreciated. I'm so ready to start using piCal -- it's just the best.

Thanks,
Paul Kaiser

Greetings!
piCal rocks, and I'm excited to use it.
I have a showstopper for now, though, and am hoping someone can help.

I just did a fresh install (on my local machine) of XOOPS 2.2.2.

I then installed the piCal 0.8 module.

XOOPS server and default timezones are set to GMT-6.
piCal is set to "value told from the server as winter time"

When I enter an event, I put in GMT-6 as the timezone for the event.

piCal treats the event as if it were submitted just straight GMT. (i.e. If I say 1600 hours with a GMT-6, it says 2200 hours...)

Any ideas what might fix this?

Thanks,
Paul Kaiser

hi Paul

Perhaps, you've missed change the timezone in your account.

in XOOPS 2.2, you have to enable the timezone option in the profile module manually.

I'm running into the same thing with a slight variation.

* My server is in GMT-6.
* My timezone GMT-6, and so reflected in my user profile.
* PiCal setting "Timezone of the server" is set to "value of XOOPS config," which is, of course, GMT-6.
* Events are entered as GMT-6.

They all display correctly to an anonymous user, but when I log in (and I assume other registered users in my timezone), they're listed 6 hours later than they should be. Of course, this also makes events listed after 5pm appear in the wee hours of the following day.

What am I doing wrong?

quite a FAQ.

Edit the timezone of your account

Greetings GI Joe,

Quote:
Where do you enable this option?

Jere

This is not an issue about my works.
You'd better ask it to www.xoops.org.

Terrific. That's all I had to do. And here I could've sworn I had set my user account time zone when I created it. Guess not.

Thanks again, Joe! Outstanding work you're doing!

I love piCal's features, but I'm having problems getting it to work right, in reference to timezones.

I have the extended profiles module, have GMT -6 in my profile, have GMT -6 as all my timezones actually.

When I add a recurring event, it adds the first instance of the event fine: the time is perfect.

All recurring events subtract 6 from my GMT-6 time.

For instance, an event I set to start at GMT-6 7pm will show up as 1pm.

It is consistent, in that every repeated occurrence beyond the first day will have the time at 1pm.

Any ideas?
Thanks GIJ!!
Paul

I downloaded piCal 0.84b and reinstalled the module completely.

Now timezone appears to not be an issue.

Either this version fixed it, or I was just doing something wrong before (with user's timezones, server timezone, etc.)

This is more an issue with date, but it may also be tied to time. I create an event on the 15th, and after submitting the event, it shows up on the 16th.

At least the event you posted looks no problem.

Check all of timezones, again.

Looks like it was a matter of my user profile in XOOPS being incomplete. My personal time zone was still set to the default, GTM 0:00. So whenever I logged in it would show the events off by 6 hours. But when I logged out it would display them correctly.

Future reference for anyone else having this problem.

I'm tired to say same answer...

Read again and Check again.
This is not a bug of piCal, but a mistake of your setting.