CiviCRM Community Forums (archive)

Jeremy,

elementValue
[...]

Ok, that looks right - I was hoping there is some problem with file reading, but that's not the case.

Now, the website is www.bluestarpr.com, and I did have to make a change to the domain name for the base url from just bluestarpr.com to www.bluestarpr.com, but I did not change this for the base directory.

Our wesbite root is at www.bluestarpr.com/site, but we have the domain redirecting to that directory so hat it looks like it would be www.bluestarpr.com and not bluestarpr.com/site.  Not sure if this makes a difference.  But our base directory path is listed as /var/www/vhosts/bluestarpr.com/httpdocs/site/media/

Don't see potential problem here (although might be missing something).

Also, for the Legacy Encoding, yes, I meant it was set by default to Windows-1252 and I have changed it to UTF8 when I export; I was referring to the delimiter field, which was set at a comma but which I have tried changing back and forth to a semi-colon to test.

Legacy encoding is used on import, so setting it on export will not have any influence. One more thing to try is to leave legacy encoding field blank and try import, however it should assume uft-8, so the same as the value you say this option has.

In general, I'm running out of ideas on what might be wrong. I think the best course of action for you is to hire somebody on Professional Services to do a quick assist for you, take a look at your install from inside and figure out the problem. I'm pretty sure it's not something very complicated, it just needs to be looked at from inside. Also, please let is know what was the problem when you solve it, so we can potentially improve error reporting if feasible, to avoid such cases in the future.

Thx,
m

I've applied the patch conditionally - if extension is available, it's used, otherwise old ways of doing things is performed.

Thx,
m

A modified version of the patch is included in 3.3 already, so your problem must be something else if you are using 3.3.