- Get Ads styles may be associated with a Site. This benefits newspaper groups with multiple sites sharing a central Layout-8000 server. When a user selects a product and run "Get Ads", they see a list of Get Ads styles. That list will include Get Ads styles that are either (a) for that paper's site or (b) not associated with any particular site. Get Ads styles for other sites are hidden. This reduces mistakes caused by choosing a Get Ads style for the wrong site. The list becomes shorter and more relevant.
- When "Get Ads" is configured to "Invoke Interface tool", the Interface tool sets adequate read/write permissions on files on behalf of the Layout-8000 user. Errors in that process are no longer considered fatal.
- A rare crash was fixed.
- Our XML interface to Miles 33 FutureProof systems improved.
- Orders with multiple rows and insertions are better handled.
- When someone stops an order, Miles 33 transmits a stop date that Layout-8000 now applies.
- When FutureProof dumps a batch of thousands of XML files during production hours, that puts a considerable load on both Miles 33 and SCS systems. In that scenario, cron asks SCS's Interface tool to start multiple scans. Our Interface tool can now detect that it is already running, note that in the "engine.log" file, and stop. The first scan is allowed to finish processing the massive batch of ads. System resources are better utilized, so that Layout-8000 users see better performance.
- Our interface to AdMarc systems improved.
- Fixed misaligned dialogs and windows.
Design & Dummy area
- Improved automatic placement of black & white ads on color pages.
- If an ad has a group request and an alternate group request but is placed in neither of those groups, it now shows up a conflict in "Show ad conflicts".
- In a magazine with 4 advertising columns, an odd-sized 1.75"-wide ad could be placed in columns 1, 2, and 4. That ad can now be placed in any column.
- The "Purge Ads" process checks Site membership. Suppose that someone is a member of site A, is authorized to work only on newspapers for site A, and was granted permission to Purge Ads. That user may purge ads at site A. This change will forbid them from purging ads at site B and ALL other sites.
- An "adpurge.log" file tracks who purged what and when.
- The Event Log tracks who purged ads when.
Article is closed for comments.