Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
When submitting attachments to tickets in 3.4.0 the following error is received
Error on finalizeMessageDisplay('resultDiv') :
Destination or is not a node or not a widget
or lastOperation or lastOperationStatus is not a node
Attachment #2 inserted '2' 'insert' 'OK'
It seems to however add the attachment fine... once this error is closed and the object is refreshed. This includes thumbnails properly displaying.
This is the only bug I've found so far with the release, so good job!
Hi,
Did you make sure to refresh your browser cache ?
Which browser / version are you using ?
Hi all,
I didn't have this issue in my tests so far.
Klaus
I did not refresh the cache, however I have also just tested on another machine and both are using Google Chrome - 28.0.1500.72 m
This error is replicated on this machine
I have attached:
1. The error image
2. The headers
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.72 Safari/537.36
Request Payload
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachementFile"; filename="IMG_16072013_170225.png"
Content-Type: image/png
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachementId"
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachementRefType"
Ticket
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachementRefId"
007646
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachementType"
file
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="MAX_FILE_SIZE"
8097152
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachementLink"
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachementDescription"
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="attachmentPrivacy"
1
------WebKitFormBoundaryMoAUOdCDUXBwZlB2
Content-Disposition: form-data; name="uploadType"
html5
------WebKitFormBoundaryMoAUOdCDUXBwZlB2--
Response Headersview source
Cache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Connection:Keep-Alive
Content-Type:text/html; charset=UTF-8
Date:Thu, 18 Jul 2013 09:57:43 GMT
Expires:Thu, 19 Nov 1981 08:52:00 GMT
Keep-Alive:timeout=1, max=100
Pragma:no-cache
Server:Apache
Transfer-Encoding:chunked
Hi,
I did not produce this issue with same version of Chrome.
The error message shows that insert is correctly done, but just return of message fails.
As this part as been changed in V3.4 to provide new "progress bar", it seems you don't get last javascript file.
Could you please refresh your browser cache and try again.
Optionnaly if it fails again, please check that your server does not cache the javascript files.
At last, please retrive /js/projectorDialog.js in your cache and post it here for a check.
thanks.
Hi,
I did not produce this issue with same version of Chrome.
The error message shows that insert is correctly done, but just return of message fails.
As this part as been changed in V3.4 to provide new "progress bar", it seems you don't get last javascript file.Could you please refresh your browser cache and try again.
Optionnaly if it fails again, please check that your server does not cache the javascript files.
At last, please retrive /js/projectorDialog.js in your cache and post it here for a check.thanks.
No problem, I have cleared the browser cache, and the test has failed. (file attached)
I have also re-uploaded the JS files in-case there was a transfer issue and cleared the cache again, and have repeated the above results.
Hi,
Could you try with another browser ?
Could you try with your Chrome on the Demo ( http://demo.projectorria.org) ?
Do you have any extension active on your Chrome browser ?
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.
You should consider your PHP Server cache.
For instance, Zend server provides some caching functionality so it will serve the old version of javascript files.
Check for how to clead this cache.
Sometime just a stop-restart of PHP server could be enough.
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
@jotrong :
You're right :woohoo:
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 :
This fix will be included in V3.5.0.
@jotrong :
You're right :woohoo:
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.4Anyway, if your provided cannot give you acces to this parameter, the fix is to replace code of file /tool/ack.php with this one :
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.
