-
Historic Monument Display: February 25, 2011 2:07
Commit 18aa078 on master, committed by Drupal Git User (LDAP)Stripping CVS keywords
-
Historic Monument Display: February 25, 2011 2:07
Commit 408e8e7 on 5.x-1.x, committed by Drupal Git User (LDAP)Stripping CVS keywords
-
Historic Monument Display: February 25, 2011 2:07
Commit a6a5d34 on 4.7.x-1.x, committed by Drupal Git User (LDAP)Stripping CVS keywords
-
Added capability to show number of associated images in monument_listbytitle
-
This commit fixes cascade deletion of related data in monument_image table. If a monument or an image with related monument_image data is deleted, then the extra data in monument_image table now gets deleted. If an image is de-associated with a monument then extra monument_image data gets deleted.
-
Fixing up code to handle access and permissions Fixing up deletion of nodes via both _delete and _nodeapi hooks
-
Corrected introduced typo in hook_nodeapi, case 'update', $node-> was missing the -
-
Really fix the bug whereby monument_image data was being recorded erroneously. Problem was also in nodeapi (case 'insert')
-
Fixes a bug whereby a monument_image could not be designated as a key_image. This was due to an incorrect query and incorrect handling of the result of the query
-
Fix a bug evident when image upload module being used Because during bulk upload of images, users cannot intervene to specify that an image is or is not a monument image, via state '-8', bulk uploaded images were being put into database table monument_image with mid=0 and monument status -9. To correct this, I have disposed of '-9' and instead, if the user does not stipulate whether the image is related to a monument or not, the module now automatically assumes that it is NOT.