uddeIM 0.5

Hi

Ok, now i understand how it works Thanks..


Just for your knowledge, regarding the problem that has been posted in this thread earlier:

"Warning: explode(): Empty delimiter. in /components/com_uddeim/includes.php on line 215"

I had the same problem, when i was upgrading from 0.4c.

I checked that all files and directories were deleted after uninstallation, then i installed the new version downloaded today.

After installation i replaced uddeim_config.php with my copy. Went to the backend and saved the config. No success, same message as earlier.

Then i tried to replace the old copy of uddeim_config.php, with the one included in the new version. No success.

I checked the versions of the files uddeim.php and admin.uddeim.php both were version 0.5b build 4.

Well after that i uninstalled the component, deleted the component link in the user meny. Reinstalled the component, skiped the old copy of my uddeim_config.php, and last but not least fixed a new componentlink in my usermenu.

And now it works just great! I have no clue what went wrong.

Again, thanks for a great component.

Bjarne

Hi,

When I try to compose a new message I get:
Warning: Invalid argument supplied for foreach() in /home/z4l0g4j/public_html/components/com_uddeim/includes.php on
line 702
below the "Recepient"

I`m running 0.5b on cb1 rc1

What could be the problem?

Thanks,
Vukan

... And Mambo 4.5.2

Hi vukan,

vukank wrote:

When I try to compose a new message I get:
Warning: Invalid argument supplied for foreach() in /home/z4l0g4j/public_html/components/com_uddeim/includes.php on
line 702
below the "Recepient"

I`m running 0.5b on cb1 rc1

What could be the problem?

This is probably the cause:

• You have turned on "Show CB connections" in the backend
• You run CB1 RC1. This CB version doesn't support connections.

Solution:

• Turn off "Show CB connections" in the backend

Please get back if that doesn't help.

Yes, that solved it.
Thanks a lot, Benjamin!

Hi Benjamin,

in the backend, tab "System->Used charset" I can't change ISO8859-1 to ISO8859-2.

The option: "Used mail charset" works properly...

I propose to introduce also 'ISO8859-2' case in "getCharsetalias" and "getCharsetMailalias" functions, if there is no other issue.

I've found the issue, the frontend doesn't accept the ISO8859-2 setting :dry:

Thanks for your work,

Post edited by: jza, at: 2006/01/18 20:27