![]() NEW TREE SHARE ROOTSMAGIC 7 PASSWORDI may lose the log of blocked notices or never get to resending ones that should have gone to you, such as password resets. phpmail() function is said to be unreliable Hostinger is recommending the use of a SMTP plugin which I am looking into.Resending notices from the Forum uses a different, valid (From:) address (but get multiplied) resending notices such as comments on blog posts fail because the address (From:) is “invalid”, despite being valid until March 2 must be an issue with the Hostinger mail server. ![]() resending notices from the WP Mail Logging plugin has revealed a bug causing them to multiply the plugin is no longer actively supported.appears to have been resolved, more or less, by adding a second MX record and revising the priority of the first in the domain – that just seems weird.starting March 2, every notice failed with an error “Could not instantiate mail function”. ![]() I’m working on correcting the problem but there seem to be multiple issues and it is proving difficult to isolate the causes: This post may not be delivered to subscribers. New subscribers probably received no confirmation email nor password reset notices. You have likely heard nothing by email from it since March 2 until yesterday and then some of you may have received flurries of duplicate messages. Please excuse the recent behaviour of this WordPress site. The following SQL script does the job and shows that it should be a pretty trivial addition to “Merge All Duplicate Citations” requiring no change to the User Interface. The problem was raised and illustrated with screenshots in a post by Tom Holden to the RootsMagic 8 Community Preview Users facebook Group.Īt the time of writing, there is no provision in RM8 to automatically or manually delete duplicate uses of citation. In this case, “Merge All Duplicate Citations” fails to deliver the desired (and logically expected) result. Outputs, such as reports, will still show duplicate footnotes for the fact. However, as of RM8 Preview 7.9.310, “Merge All Duplicate Citations” can result in duplicate ‘uses’ of the merged or master citation where there were previously duplicate but independent citations linked to the same fact. This is an example of improved database normalisation.Ĭoncomitant with this change is an added feature “Merge All Duplicate Citations” whose effect is to replace all records in the CitationTable having the same Master Source and matching text fields (Citation Details) with one record linked via the CitationLinkTable to all the facts that its duplicates were previously attached. The one set of citation data then becomes a ‘master’ citation whose edits then carry through to all ‘uses’ of it, just as revisions to a Master Source affect all citations of it in all versions of RM. RM8 adds the CitationLinkTable which allows one set of citation data to be linked to or ‘used’ by multiple facts. To use the same citation data for more than one fact meant that it had to be replicated in another record, making revisions to the data repetitious and onerous. RootsMagic 8 introduced indirection between citation data (text fields) and the fact to which a citation is attached, In RM7, the citation data and linkage was combined in the CitationTable. or this could be TemplateID = a specific template number, to just change one template WHERE (SourceTable.SourceID = CitationTable.SourceID) WHERE SourceTable.SourceID = CitationTable.SourceID ) SET (Fields) = (SELECT cast(Replace(cast(CitationTable.Fields as Text),'','CitItemD' || SourceTable.Name || '') as blob) add extra field for name - at the start so it is used for citation name when converting to v8 or this could be TemplateID = a specific template number to just change one template SET (FieldDefs) = cast(Replace(cast(FieldDefs as Text),'','CitItemDItem NameTextItem NameTo distinguish citationsTrue') as blob) This will only work for user templates, not for supplied ones (SourceTable.TemplateID > 10000)Īdd in new field - CitItemD for citation name and put in source name - creates good citation name in RM8 I have taken advantage of this concatenation to get meaningful names by inserting a new field in my own templates as the first one in a citation and then setting the value in the citations to the source name. So I run this script on my RM version 7 database so that it is ready for importing into RM version 8. ![]() In RM8, citations are re-useable and have a name which is made by concatenating the contents of the citation fields.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |