jjjj12212 / EPESI-Ical

Export EPESI CRM Calendar to other Calendars
GNU General Public License v2.0
3 stars 1 forks source link

Problem with .ical content file generation #6

Closed kbies closed 10 years ago

kbies commented 10 years ago

Hello,

I have a problem with correct generation of .ical content;

/* My steps */ I downloaded the source code files properly;

Installed it following by instruction steps;

I have done the step -->My Settings->Control Panel->Calendar Export Settings --> I checked all chceckboxes and typed my domain;

After this step the system correctly generate a ID;

This step was everything ok;

A go: Menu->CRM->Calendar and clicked on "Export Calendar"

/* Problem effect / The effect of working this script is gerenated *.ical file <-- the file shows itself;

I opened (everytime when I open) this file by Notepad++, inside exists the comment:

" Invalid uid, Please use a different uid or generate a new one in Menu->My Settings->Control Panel->Calendar Export Settings "

/* What I checked ? */

/* My observations, conclusions */

Please tell me some hint or suggesion whats could be wrong and how to correct it;

jjjj12212 commented 10 years ago

Hi kbies,

we haven't had a chance to make some modificatioins with the latest version of EPESI. We will take a look at this and try to update the project for you.

jjjj12212 commented 10 years ago

Hi Kbies,

We have updated the package, please download the latest changes and overwrite the existing files. If your still having an issue, please let us know.

jjjj12212 commented 10 years ago

If your still having a problem Kbies, can you do the following:

turn on only meeting in the settings. for domain, put in .com

Check and see if that works.

kbies commented 10 years ago

Thank you. It works. The content of file is gereated;

It works also not even for .com domains;

It works for every option - meetings - tasks - phonecalls;


/* Issue number 2 */

In the .ical content file exists an incorrect characters caused by incorrect character encoding (charset) (for my language).

Could you help me to apply UTF-8 charset to .ical file ?

jjjj12212 commented 10 years ago

Kbies, lets try this:

modify modules/Premium/Ical/ical.php

change line 25 from:

header('Content-Type: text/calendar');

to

header('Content-Type: text/calendar; charset=UTF-8');

Let me know if that works..

regarding about the .com , I actually put in company.com as an example, not sure why it only showed .com but it was only an exmple though, glad that were progressing. :)

jjjj12212 commented 10 years ago

If that didn't work, also try this:

header( 'Content-Type: text/calendar; charset=utf-8' );

kbies commented 10 years ago

Yes, I tried this method, but its doesn't work (maybe it works, but doesn't solve my problem with characters )

In database I have correct characters (without any errors ) in utf8_unicode_ci encode format.

In export .ical file I don't have that kind of characters like: ą , ę , etc

So in my opinion it has to be something with charset encoding;

Do you have another idea ?

kbies commented 10 years ago

I also tried open each php file of ical by classic Notepad and save it in UTF-8 charset by hard and uploaded that files on server --> It also doesn't solved the problem

jjjj12212 commented 10 years ago

Hi Kbies, ^ yeah I don't think that will give you the results you need, good try though :)

My Database also uses that encode format.

Can you post the actual data that is inside your database so I can copy, paste and test it?

Also what Calendar application are you exporting it to so I can test that as well?

Can you also, on the EPESI Forums, PM me your issue so I can send you my email address and you can attach the .ical so I can take a look at it.

I would put my email address here but I will get spammed.

Thanks.

jjjj12212 commented 10 years ago

same username in EPESI FYI

kbies commented 10 years ago

Are you using this forum --> http://forum.epesibim.com/index.php ?

Sorry, I found you.

jjjj12212 commented 10 years ago

Sent you a private message on the EPESI Forum

jjjj12212 commented 10 years ago

This solution was solved. On line 53, you need to add: $mysqli->set_charset('utf8');

which pumps out the correct characters from the database.