3.4.0 - Attachment error

Demo does work, I shall make a new installation. This could be down to SQL query being ran manually against the database and not using your inbuilt updater.

Thank you for your help, I'll consider this closed as the demo shows it's clearly working. Worth noting the install was 3.3.2 and updated to 3.4.0.

I've just had the same problem and find out the reason for it.
It due to magicquotes.
So, in the php.ini (or can change to php5.ini), we can put this line:

magic_quotes_gpc = off;
magic_quotes_runtime = Off;
magic_quotes_sybase = Off;

After we may face again the problem, it's because of the server will take time to take effect for this change.

For my case (I use host Godaddy), what I did is:

1. Log in to Account Manager.
2. From the Products section, click Web Hosting.
3. Next to the hosting account, click Launch.
4. In the Hosting Control Center, click the System Processes icon.
5. Click End Web and follow any prompts.
Reload the program and it works

babynus wrote: @jotrong :
You're right
I enabled magic_quote_gpc and could reproduce the issue

@Rexeh :
jotrong's advise is the best : disable magic_quotes_gpc.
This directive in obsolete in PHP 5.3 and deleted in PHP 5.4

Anyway, if your provided cannot give you acces to this parameter, the fix is to replace code of file /tool/ack.php with this one :

<?php
/** ===========================================================================
 * Acknowledge an operation
 */
if (array_key_exists('resultAck',$_REQUEST)) {
  $result=$_REQUEST['resultAck'];
  $result=str_replace('\"','"',$result);
  $result=str_replace("\'","'",$result);
  echo $result;
} else if (array_key_exists('resultAckDocumentVersion',$_REQUEST)) {
  $result=$_REQUEST['resultAckDocumentVersion'];
  $result=str_replace('\"','"',$result);
  $result=str_replace("\'","'",$result);
  echo $result;
} else {
	echo("ack type not recognized");
  echo 'errorAck';
}
?>

This fix will be included in V3.5.0.

Thanks, but also couldn't reproduce this issue once I had setup from fresh on our server a while back. Must have been something going from LOCAL and copying the code and bringing it in other server.