The httpd process is starting without any problems, but when I to access the document root of the server like
then it ends up with an error 403 “Forbidden”.
I have already checked the file system permissions for my document root folder, which is:
0 drwxr-xr-x 3 root system 256 Feb 11 12:35 .
4 drwx—— 23 root system 4096 Feb 11 12:35 ..
4 -rwxr-xr-x 1 root system 1184 Mar 07 2012 http_server_styles.css
0 drwxr-xr-x 2 root system 256 Feb 11 12:35 images
4 -rwxr-xr-x 1 root system 3491 Mar 07 2012 index.html
So there is read permission for “other”, which should be fine.
Any idea what’s wrong here ?
*CREATE OR REPLACE TRIGGER WERD.VERIFY_UPDATE
NO CASCADE BEFORE UPDATE OF ATTR0000001069
SIGNAL SQLSTATE ‘75000’
SET MESSAGE_TEXT=’Update can only be done by Supervisor’;*
But when executed via ICN , the error number responded is different.
“explanation”: “The item might be checked out by another user, you might not have the appropriate permissions to edit the properties of the item, or the item might be referenced by another item in the repository, which prevents the item from being edited.”,
“userResponse”: “Refresh the results and try to edit the properties of the item again. If the problem persists, ask your administrator whether the item is referenced by another item or whether you need different permissions to edit the properties of the item.”,
“text”: “Your changes cannot be saved.”
Looks like the error number is not the same thrown by the trigger.
How do I capture this actual SQLSTATE signal ?
When calling the collapseMultipleParties transaction (which adds a new party), I’ve noticed that the extension is not being triggered. Stepping through the code using a debugger, I’ve found that when the collapse transaction creates the new party, it calls the addPartySimple method in the TCRMPartyComponent class instead of the regular addParty.
My question is: Since I cannot extend the functionality of addPartySimple (it does not show up in the workbench, when adding an extension), how do I force triggering of my extension?