Error with a trigger on site metadata

Squiz Matrix Support
1

I am using squiz v3.18.6


I have a site setup with some metadata on it.



I have a trigger set up to fire when the metadata on the site is updated.



When I update the site metadata I get the following error:



Fatal error: Maximum execution time of 30 seconds exceeded in /usr/local/mysource_matrix/core/lib/DAL/DAL.inc on line 594

Warning: Unknown: ORA-01013: user requested cancel of current operation in Unknown on line 0



All the trigger is doing is setting the metadata value of another asset.



I have other triggers set up in the site and they all work fine.



Does anyone have any advice on this error message. It would seems like a PHP/Oracle error to me rather than a Squiz error!



Just tried deleting the metadata from my site and get the following error:



Fatal error: Maximum execution time of 30 seconds exceeded in /usr/local/mysource_matrix/core/lib/DAL/DAL.inc on line 641



Think there maybe something major wrong with the installation!!??



Cheers.

2

[quote]I am using squiz v3.18.6


I have a site setup with some metadata on it.



I have a trigger set up to fire when the metadata on the site is updated.



When I update the site metadata I get the following error:



Fatal error: Maximum execution time of 30 seconds exceeded in /usr/local/mysource_matrix/core/lib/DAL/DAL.inc on line 594

Warning: Unknown: ORA-01013: user requested cancel of current operation in Unknown on line 0



All the trigger is doing is setting the metadata value of another asset.



I have other triggers set up in the site and they all work fine.



Does anyone have any advice on this error message. It would seems like a PHP/Oracle error to me rather than a Squiz error!



Just tried deleting the metadata from my site and get the following error:



Fatal error: Maximum execution time of 30 seconds exceeded in /usr/local/mysource_matrix/core/lib/DAL/DAL.inc on line 641



Think there maybe something major wrong with the installation!!??



Cheers.[/quote]



At a guess your trigger is being applied recursively, so the update of the metadata on the other asset is firing another trigger. Its hard to tell without seeing the system though.

3

I'll have a look and see if I can see if there is a loop.


Thanks for the pointer.