Lightroom 5.3 bug fixes.

Lightroom 5.3 is a 800MB download. Where can I get a sensible size file just for the bug fixes?
Also where is there a list of the fixes? The readme file gives nothing usefull.

in your lr5.2, click help>updates...
bug fixes:
Issues when upgrading catalog from previous versions of Lightroom.
Incorrect photos are displayed after switching away from a Publish Collection.
Catalog optimization did not finish, and was not optimizing the catalog
Feather of clone spots is set to 0 after upgrading catalog to Lightroom 5.
Auto White Balance settings are not saved to Snapshots.
Sony 18-55mm lens is detected as the Hasselblad 18-55mm lens for lens correction.
Increased Update Spot Removal history steps when in Before and After view.
Slideshows start playing automatically even when the Manual Slideshow option is enabled.
Video playback stops when dragging on the scrubber.
Errors when publishing photos to Flickr through the Publish Service.
Option + drag on Edit Pin behavior is functioning incorrectly.
Black border appears around the exported slideshow video.
Catalog containing images processed with PV2003 were adding a post-crop vignette when catalog upgraded to Lightroom 5.
Pressing the “Reset” button while holding down the Shift key caused Lightroom to exit abruptly.
Output Sharpening and Noise Reduction were not applied to exported images that were resized to less than 1/3 of the original image size.
The Esc key did not exit the slideshow after right clicking screen with mouse during slideshow playing.
Import dialog remained blank for folders that contain PNG files with XMP sidecars.
Metadata panel displayed incorrect information after modifying published photo. Please note that this only occurred when metadata was changed after the photo was published.

Similar Messages

Bug Fix Lament

Adobe: It does not bode well for Lightroom to have relatively-easy-to-fix bugs persist, release after release.
I highly recommend finding a way to get more of them out between releases.
In my opinion, one should almost be able to assume certain bugs are not there since they were reported well in advance of latest release - just like we can assume certain popular new cameras will be supported...
If I remember correctly, there was precisely one item on the "known issues" list of the 3.3 release - hiding them does not make them go away.
Rob

Lightroom 3.3 Bugs Fixed below (these are probably the major bugs, and there may be many more minor ones not listed). It would seem that they weren't exactly sitting on their hands.
Bug fixing is about priority and risk. If a bug fix has a high risk of creating other bugs and a low priority because of few users affected or easy workarounds, then it might be better to leave it alone. It's also possible that bugs that seem easy to fix actually require a near entire rewrite of entire sections of code.
Edit in PS CS4 from LR 3.2 did not give option to render to TIFF/PSD
Process Version defaulted to PV 2003 when Lightroom’s installed Develop Presets are applied on Import
All Auto-ISO values were not properly handled for the Nikon D3s
An error could be generated when sorting by “User Order” in Collections
There was an incorrect Profile Name tag for Canon 18-55 and 17-40 lens profiles
Facebook album selection only displayed up to 25 albums
Lightroom 3 could fail to launch Photoshop CS5 if Photoshop CS4 was uninstalled after the Photoshop CS5 installation
Numerous cloning or healing spots could have caused Lightroom to become unresponsive
Lightroom could have crashed when the metadata filter is selected and the grid is displaying all images in the catalog
Lightroom 3.2 could have failed to import all of the images from an iPhone 4
Some Sigma X3F raw files were rendering incorrectly
Choosing the “Make a second copy to” option on import would result in incorrect folder structure for the second copy
Resetting the crop angle by double-clicking the Angle slider removed a custom aspect ratio
A tooltip for the Japanese language version of Lightroom 3 displayed the wrong keyboard shortcut for “Flag as Pick”
Paste Settings did not apply to all images in the Develop module Filmstrip
Smart collections in Lightroom 3 did not use the same definition of “All Searchable Metadata” previously available in Lightroom 2
Text watermarks or portions of text watermarks could have failed to be applied to images on export
SmugMug publish collection dialog included a mixture of English text when using a language setting other than English
Lightroom would not import files from the Panasonic LX5 that were shot with the iZoom Function set to above 90mm
Choosing the Limit File Size option in the export dialog could have stripped certain EXIF fields from the exported file
The Targeted Adjustment Tool may have performed slowly in the Lightroom 3.3 release candidate
A single image published to multiple collections for a single publish service did not display comments properly
Updating an existing Develop preset with all settings could have failed under certain conditions
The watermark drop shadow settings behaved differently in Lightroom 3.2 when compared to Lightroom 3.0. They have been returned to the Lightroom 3.0 behavior.
The YYYYMMDD file renaming option was not available when the Lightroom language setting was set to Dutch
An existing Smart Collection updated to filter for all photos with “Ratings is Zero” would show all images in the catalog
Publishing an empty category to SmugMug would cause an error
JPEG exports in the Lightroom 3.3 Release Candidate were significantly slower than the same export process in Lightroom 3.2.
A graphical Identity Plate included in output was not correctly color managed
Deleting all images in a Flickr photoset could have caused Lightroom to return an error message
Changing the sort order to “User Order” while in Survey View on the Mac may have caused an error to appear
Lightroom could have failed to respond when viewing an image containing numerous cloning or healing spots at 1:1 view
RGB values were not displaying properly in the white balance tool
The Smart Collection criteria “Folder starts with” was not working properly
The navigator panel in the Develop module would incorrectly display threshold information when holding down the alt or option key and applying adjustments
Applying a flag, star or label setting to an image via the toolbar in the Develop module while in auto-advance mode would result in an incorrect setting display for the subsequent image
The application of color noise reduction at low color temperatures (e.g., tungsten or candlelight) could have provided results below our quality standards

Lightroom 5.3 bug with export images

Hi,
I can't export single images in Lightroom anymore. When I choose an image including the watermark the system exports all the latest imported images, but not a single one. Can anyone help me with that?
-jo

in your lr5.2, click help>updates...
bug fixes:
Issues when upgrading catalog from previous versions of Lightroom.
Incorrect photos are displayed after switching away from a Publish Collection.
Catalog optimization did not finish, and was not optimizing the catalog
Feather of clone spots is set to 0 after upgrading catalog to Lightroom 5.
Auto White Balance settings are not saved to Snapshots.
Sony 18-55mm lens is detected as the Hasselblad 18-55mm lens for lens correction.
Increased Update Spot Removal history steps when in Before and After view.
Slideshows start playing automatically even when the Manual Slideshow option is enabled.
Video playback stops when dragging on the scrubber.
Errors when publishing photos to Flickr through the Publish Service.
Option + drag on Edit Pin behavior is functioning incorrectly.
Black border appears around the exported slideshow video.
Catalog containing images processed with PV2003 were adding a post-crop vignette when catalog upgraded to Lightroom 5.
Pressing the “Reset” button while holding down the Shift key caused Lightroom to exit abruptly.
Output Sharpening and Noise Reduction were not applied to exported images that were resized to less than 1/3 of the original image size.
The Esc key did not exit the slideshow after right clicking screen with mouse during slideshow playing.
Import dialog remained blank for folders that contain PNG files with XMP sidecars.
Metadata panel displayed incorrect information after modifying published photo. Please note that this only occurred when metadata was changed after the photo was published.

Will Adobe charge for 'bug fixes'

Hello,
I'm not trying to be sarcastic here, but I'm really interested. I know Adobe always charges for any upgrades to their software/apps. I'm not sure what they consider Lightroom 1.0 - that is, if they consider it fully cooked and any changes to it would be considered an 'upgrade' or if bug fix releases will be made, free of charge to customers who have purchased 1.0. To me, it probably was released for a charge a little early, and hopefully I won't have to pay for a more stable app.
Regards,
Kevin

Thanks. Do any insiders have an idea when a bug fix/release may occur? I would hope it would be before the price goes to $300.
I pesonally tried the product first using the trial (not for the full 30 days) and decided to buy it ($199), mainly based on the very good develop module, and I guess the hype and promise of the Adobe literature. I really hope some of its shortcomings in workflow (and I don't mean anything that goes against its basic design) is included in one of these interum releases soon, and is not looked upon by Adobe as an 'upgrade' release for more money.
Regards,
Kevin

Have a problem with Lightroom 5.4. Since the program crashed yesterday it won't launch, it comes up with the message "Lightroom encountered an error when reading its preview cache and needs to quit". " Lightroom will attempt to fix this problem net ti

Have a problem with Lightroom 5.4. Since the program crashed yesterday it won't launch, it comes up with the message "Lightroom encountered an error when reading its preview cache and needs to quit". " Lightroom will attempt to fix this problem next time it launches". Except that it doesn't, I keep getting the same message and the program closes. Does anyone know what I can do to repair it? Can't back up, can't do anything.

There are dozens of threads in this forum that describe the fix

My ipad just won't let me enter my apple password on FaceTime or iMessage, it works fine on my iPhone, I have tried numerous things but nothing works, can anybody help please, will a bug fix sort this out when they finally make one

My ipad just won't let me sign in with my apple password on FaceTime or iMessage since updating to ios7 it says check my network connection, even though my iPhone works fine with the same password, can anybody help please, I have tried numerous things but nothing works. Will I have to wait for a bug fix to sort this? I hear they are working on one a the minute, I hate ios7

Try a Restart.
Press and hold the Sleep/Wake button for a few seconds until the red "slide to power off" slider appears, and then slide the slider. Press and hold the Sleep/Wake button until the Apple logo appears.
Resetting your settings
You can also try resetting all settings. Settings>General>Reset>Reset All Settings. You will have to enter all of your device settings again.... All of the settings in the settings app will have to be re-entered. You won't lose any data, but it takes time to enter all of the settings again.
Resetting your device
Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears. Apple recommends this only if you are unable to restart it.
Or if this doesn't work and nobody else on the blog doesn't have a better idea you can contact Apple.
Here is a link to their contacts with most of the information below.
http://www.apple.com/contact/

List of Bugs Fixed in JDev 3.2.3

Several users requested a list of bugs addressed in JDeveloper 3.2.3. Here is a list:
Bugs Fixed for DAC
Infoswing Frame Could Not Be Closed. (1729167)
Validation Methods Are Invoked During Removing Of A New Row From Gridcontrol (1727214)
Regrn:Lov Control: All Fields In Dept Are Listed Instead Of The Selected One. (1724885)
Regrn: List Control Unbound Once Rollback. List Control Is Empty (1723467)
Regrn: Value For The Last Field Doesn'T Get Saved In The Database. (1723367)
Remove The Commit/Rollback Limitation From Findpanel (1720412)
Abm: Rowsetaccessimpl.Absolute() Does Not Check For -1 On Call To Getrangestart (1719841)
Canceling Closing Of Infointernalframe Doesn'T Work (1718994)
Viewlinkinfo Objects Are Not Nested Application Module Aware (1717528)
Viewlinkinfo Objects Generate Illegal View Link Names (1717507)
Dac Lov Controls Are Not Binding To Dataitems (1717492)
Entity Validation Handling Problem In Dac Gridcontrol (1717482)
Trw - Rollback Reexcutes All Queries (1715674)
Getestimatedrowcount Is Called Unnecessarily (1709897)
Rowsetinfo - Error Message Needs More Details (1692843)
Nls: Translated Button Labels Are Shown As Squares In Styleeditor (1688651)
Abm: Blank Rows Created In Grid In Mapping Wizard'S Summary Page (1680610)
Validaterow Is Not Called If You Leave The Row From Non-Modified Column (1671182)
Textareacontrol Color Will Be Gray Always If Run In Jdev With Jdk 1.3 (1666518)
Qabk: Infoswing Control Dialog Box Throws Exception At The Run Time (1665341)
Sessioninfo.Close() Does Not Close The Database Session (1664400)
Nls Business Component Data Form Runtime Missing Translations (1652484)
Qablk Tree Control Picks Up And Displays Only First Selected Rowset (1647498)
Abm: Nullpointerexception Is Thrown When Detail Button Is Used In Visual Trace (1647449)
Rowsetinfo.Publishrowset Does Not Restorec Revoked Rowset. (1640653)
After Setting Validation To Row Level Messages Appear More Than Once. (1640604)
Detail Row Inserted Via Entity Object Is Not Displayed Automatically. (1633778)
Dac-106 Trying To Set Nullable Date Column To Null If A Date Format Is Used (1633564)
Memory Leak When Closing And Reinstantiating Internal Frames (1631899)
Issuing Rollback/Reexecute Query Resets Query Find Criteria (1631795)
Rows Inserted In Vo Not Displayed On Gridcontrol When Rowset Is Published (1625827)
Data In Grid Control Is Lost After Applying Filter And Performing Updates (1624068)
Data Does Not Display In Comboboxcontrol (1623945)
Abm: Find Button In Filter Control Should Be Default For Enter Key - Posco Issue (1584634)
Abm: Sorting On Filtered Grid Control Clears Filter - Posco Issue (1584627)
Last Record Is Not Displayed When Scrolling Thru A Grid Control With Jdk 1.3.0 (1583918)
Abm: Findcontrol Gets Built Everytime The Navigation Bar Is Bound To A Dataitem. (1527169)
Rowset.Setqueryonopen(False) Does Not Prevent The Grid From Populating Itself. (1527158)
Find Panel Custom Editor Option Does Not Work (1511669)
Addmasterlinkinfo -- No Such Method, Should Be Addmasterlink (1503508)
Abm: Sql Error When Findcontrol Is Used The Second Time - Posco Issue (1477081)
Bugs Fixed for BC4J
Insert A Row Using "Immediate Loading" Causes Nullpointerexception (1766124)
Apps: Jdbc Statement Not Being Closed In Viewobjectimpl.Closefreedstatements() (1765387)
Appsjperf: Bind Indexes Changes For Different Users For Inserting/Updating Eo'S (1761569)
Data Page: Query Form Generates Incorrect Query If Attribute Name != Column Name (1756150)
Classcast Exception: Createviewobject() Not Returning Remote Vo Subclass In Visi (1742764)
Samples: Tester Project Does Not Compile, Prevents Use Of Tester To Debug (1720551)
Samples: Inserting A New Item Into The Auctions Database Fails To Insert Dbrecor (1718004)
Samples: Bc4jauctions.Html Adding An Item To Auctions Db Instructions Has Error (1717988)
Samples: Bc4j Auctions Sample Sign Me Up Link Throws Exception (1717967)
Qablk: Required Libraries Are Not Included In The Bc4j Project (1714268)
Datapage Wizard Cannot Generate Anything (1713272)
Datapage Wizard Should Use "Iso8859_1" As Default Encoding (1705620)
Nls: Japanese Characters Are Garbled In "Show Data As Xml" Dialog In Jbo Tester (1700430)
Can Not Include Xml File Using Xsql:Include-Xsql (1700125)
Nls: Error Message In Bc4j Jsp Application Is Garbaged (1695391)
Nls:Web Bean Wizard Does Not Register Web Beans To Web Object Manager Correctly (1693941)
Nls: Js Tab Container Web Beans Cannot Display Japanese (1690456)
Inputdate Doesn'T Allow Field Editing By User (1689571)
Nls:Descriptions For Some Hilo Charts Are Not Shown In Jsp Element Wizard (1684559)
Nls: Truncated Help Button In Add Servlet Dialog Of Web Object Manager (1677201)
Nls: Truncated Button Label For 'Reset' In Query Dialog Of Data Form Runtime (1675129)
Wrong Tip For Js Tree Control Web Bean In Jsp Element Wizard (1673107)
Application Pool Generates Cookies Containing Commas (1667201)
Noclassdeffounderror When Try To Run The Tester In Three-Tier Mode. (1665040)
Using Am In Am Pool 2nd Time (Even Times) Causes Jbo-25302 (1664901)
Apps: Vo.Setattributeinternal Causes All The Rows To Be Brought In From Db. (1663724)
Ora-29534/Ora-29545 When Deploying Bc4j Runtime Classes (1661861)
Nls: Too Small List Box And Truncated List Items In Jsp Element Wizard (1660075)
Nls: Jbo-27022 Cannot Navigate Through Japanese Data With Bc4j (1660065)
Web Object Manager Truncated Label In Edit Webbean Dialog (1658304)
The Datapage Wizard Does Not Generate Code To Display Each Attributes In Vo. (1656532)
Nls: Jsp Application Runtime Missing Translations (1647710)
Labels In An Entity View Are Not Displayed Correctly (1640869)
Nls: Horizontal Alignment And Translation Problem In The Jsp Element Wizard(Edit (1636848)
Nls: Instruction Of Webnew.Java File Missing Translations (1636779)
Query Collection Shouldn'T Be Blown Away If Maxfetchsize = 0 (1634721)
Jbo-25014 Exception For Intermedia Domains (1634452)
Cannot Create A Viewlink Between A View In A Local Am And One In An Imported Am. (1631834)
Apps:Rowset Interface Should Also Provide Removerowsetiterator Method (1604934)
Extra Spaces Before ';' And Minor Typo For Visibroker In Jbo Resource Files (1585159)
Typo In A Webobject Resource File: "Xqsl" For Xsql (1585124)
Apps: Enhanced Stateless With Affinity Support For Viewobjects (1576128)
An Exception Occurs When Run The Database Setup File For Bc4j (1563286)
Apps:View Object Wizard Gives Incorrect Error Message With Invalid Extend (1562030)
Apps: Cannot Override 'Extends' Class In The View Object Wizard (1561990)
Ias 10210 Nt M1: Jsp Error While Going To The Online Orders Window (1554391)
Apps: Returns No Row For A Detail Rowset Even Though Such Row Exists In Db (1554209)
Mats: Bc4j Samples Not Working Correctly (1542381)
Nosuchmethodexception Using Bc4j Design Time With Xml Parser 2.1.0 Beta (1527368)
Cap Gmac: Insert Problem After Upgrading From 3.1 (1524873)
Nls: New Xsl File Needs Output Encoding Tag (1473212)
Createuser.Sql Needs To Be Provided To Customers (1449624)
Ias 9i: Bc4j Installer Needs To React To 3.2 Tutorial Changes (1411505)
Nls: Ias1.0.2 M3: Jsp Bc4j Application Cannot Insert Record (1404390)
Bugs Fixed for JDev IDE
Webtogo Displaying Stale Pages. (1761657)
Nls: Datapage Application Updates Multibyte Data Incorrectly On Webtogo Server (1746080)
Integration Or Cache Problem With Web-To-Go (1741134)
Nls: Translated Booknotfound.Html And Nojavadoc.Html Are Not Installed (1738859)
Nls: Html Help Cannot Be Installed With Japanese Build (1738854)
Nls: Japanese Html Help Has Wrong Folder Structure In The Contents Tab (1737050)
Nls: Cannot Register Servlet Using Web Object Manager (1736178)
Nls: Import Library Utility Is Not Translated And Doesn'T Support Japanese Char (1724029)
Repository Source Control Workarea Picker Does Not Work In Jdk 1.3 (1717231)
Nls:Error And Warning Are Garbled In Setting Encoding Of Compiler To "Cp1252" (1716640)
Nls: Popup Menus "Open" And "Edit With Oracle Jdeveloper" Are Not Translated (1684565)
Qablk:Jdeveloper Crash When Opening Frame In The Ui Design Mode In Windows 2000 (1683235)
Nls: Overtranslated Parameter Names In Created Dialog (1677246)
Nls: Comment 'Constructor' In Application, Class, Sqlj, Beaninfo Not Translated (1677241)
Nls:Error Message Is Different Between Locale = Us And Ja (1671222)
Nls: Cannot Select More Than One Jar/Zip File When Adding Paths (1660130)
Nls: Cannot Run Jsp Application Using Bc4j Created With Japanese Tables (1660019)
Nls:Unable To Insert/Update For Bc4j Jsp Application On Ias 1.0.2.0 (1656603)
Nls: Httpservlet Code Is Incorrect (1650724)
Nls: All Web Object Wizards Behaviour For Character Encoding Should Be Unified (1650722)
Nls Enterprise Javabean Wizard Truncated Translations (1645621)
Nls: A Message 'Loading Jsp' Missing Translation In The Jsp Runtime (1636889)
Unable To Invoke Dependency Manager (1630723)
Incorrect Otn Link Specified In Creating_Html_Clients\Srv_Pxsqlservlet.Html (1618656)
Must Use Thin Jdbc In Order To Solve Nls Problems With Repository Tools (1534551)
Nls:Webtogo Doesn'T Find Jsp Pages With Japanese Names. (1477338)
Nls:Japanese Character Corrupted When Sql*Plus Invoked From Jdeveloper (1461164)

Hi Steve
Many thanks for that. Could I ask that
this kind of thing goes in the release
readme also.
Marc

May Release: New partner support, Infrastructure updates, Site templates and bug fixes

Link: http://www.businesscatalyst.com/_blog/BC_Blog/post/May-release-New-partner-support-Infrast ructure-updates-Site-templates-and_bug-fixes/
We are announcing a new Business Catalyst release, scheduled to go live on Thursday, May 3rd. With this release, we are continuing our investments in system performance and stability by increasing our web servers capacity, enabling HTTP acceleration to provide faster site loading times, and improving the site creation speed by using pre-generated sites.
On the product side, we have completely revamped our partner support workflow taking advantage of the Adobe support infrastructure and tools, enhanced the site templates workflow for partners, and included lots of bug fixes and improvements. Read through the following sections to get detailed information about this release:
Partner support
Infrastructure updates
Features and enhancements
Issues fixed by this release
What's next
You can jump to the corresponding section by clicking the above links.
Partner support
Updated Help & Support partner experience
Following Adobe ID support, we have upgraded BC support tools (cases, chat, documentation) with standard Adobe tools. As a partner, you can now benefit from the same support tools as the rest of Adobe Creative Suite, and can track your support cases with Adobe BC, Dreamweaver, Muse or Photoshop in a single place.
Partners with more than 100 paid sites will get 2nd level chat support, which includes a higher priority, by default. If you have more than 100 paid sites, but spread across different Partner Portals, please ask support to enable 2nd level chat for you.
Support experience for your Small Business owner clients can now be owned by partners (see below).
Custom Help & Support URL for your clients
As a partner, you are probably already offering various additional services to your clients besides building & maintaining their BC site. Support, tailored specifically to your client needs, is usually one of these value-added services. We are now enabling you to take your Support service to the next level. In Partner Portal Settings, you have the option to set a custom URL for what will open when your client clicks on Help & Support inside Admin Console:
If you have multiple partner accounts, for different verticals, you can specify a Support URL for each of these.
The default Support experience provided by BC for your clients will be updated in a few releases to be similar to the partner support experience. This includes BC-branded support cases and documentation. If you'd like to keep a white-label experience for your customers, please set your own Help & Support URL in Partner Portal.
For more details please read the Improved support workflow and new forums announcement on our blog.
Infrastructure updates
Between our April release and the following infrastructure updates have been enabled
Limited trial sites for free partners – starting with our May release, the number of trial sites a Free Partner can have will be limited to 100. Once the limit is reached, Free Partners that need to create a new trial site have the options to upgrade to a higher partner plan, upgrade some of the trial sites to paid or delete unused/expired trials.
Automatic trial expiry extension - with this release, trial site expiry date will be automatically extended with 30 days every time an admin user logs in the system through the admin interface or through FTP.
Installed additional hardware - we have installed additional web servers on all our data centers, that translate into an increase of the existing capacity with over 70%.
Updated DNS infrastructure - we have improved the DNS resolution for email delivery so that we can increase the rate at which we're sending the system operational emails
HTTP acceleration – all sites static assets are served from a new cache engine (images, CSS and JavaScript files, together with improved headers that should allow the browser to cache them better for a browsing session). This update has been turned on along with our April release, and has made all the BC sites load faster on first and on subsequent loads.
Accelerated site/partner creation – we've changed the way new sites are created for faster speed, pre-creating them and reusing pre-created sites when needed, and have also improved the creation process for new partners, minimizing the impact of new CCM customers on the existing datacenters.
Adobe ID for partners - in order to support an integrating experience between the various Adobe tools a partner may use (Dreamweaver, Muse, Support forums) we have added Adobe ID support for Business Catalyst partner accounts. Starting April 19, partners are asked to merge their current Business Catalyst account with their Adobe ID accounts. For more details about the transition process and FAQ please read the Introducing Adobe ID blog post.
Updated Terms of Use - Along with several other changes in our processes in the past few months, we also revamped our Terms of Use and the signature process by requesting every admin user to sign a TOU. We have completed the rollout for partners, and we might be pushing an updated partner Terms of Use version within the following weeks. For more details and questions about this change, read the New Terms of Use for Business Catalyst blog post.
Features and enhancements
Site templates
To support the increasing number of partners building, sharing or reusing templates to create new sites, we're extending our site templates support from our partner portal with a new template type and improved management support. The update is going to enable partners to mark sites as templates and choose between making them available in Online Business Builder and keeping them private in their partner portal. A template site will not expire and has the same limits as any other trial site.
Based on your partner level, you can create private or public templates using the Site Details screen or the Tools>My Site Template section from your Partner Portal. Standard partners can only create private templates, while Free Partners can only view site templates that have been transferred to their accounts by other partners.
The number of templates a partner will have will be limited and will vary based on partner level: free partners can store up to 5 templates in their partner portal, standard partners have up to 100 site templates while Premium Partners might have up to 200 templates. Paid sites marked as templates are not counted against these limits.
Business Catalyst Partner fixes
While we are really focused on making the Business Catalyst integration into Creative Cloud a smashing success, we are slowly resuming our efforts to deliver fixes that have been requested by our partners. This release includes the following partner fixes:
Improved product custom fields - we have increased the maximum number of characters for product custom fields to 1024 (previous limit was 256); this gives partners and customers additional space to use when working with products
Improved Secure Zone subscribers list - we have added the customer email address in the Secure Zone Subscribers list to enable partners better filter and manage customers
Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
Social plugins integration updates
Starting with our May release, we are updating the social plugins support to require users to get the plugin code from the third party provider and saving into his Business Catalyst website. The module tags and configuration will remain unchanged, but will render an empty tag until the partner or site owner will update the module template to include the corresponding module code snippet from the third party platform provider.
For more information about how you can enable the Social Plugins on a Business Catalyst websites, read the Social Media: Integrating Facebook and Twitter knowledge base article.
Other changes
Updated weekly emails - Starting with our May release, the information in the site weekly emails has been filtered based on the site's plan. For example, webBasics site reports will no longer include the sales report.
Localization - we improved and increased the coverage of the admin interface translations into German, French and Japanese
Site Settings -> Ignored IP addresses has been relocated under Reports -> Visitors -> More.
BC-Dreamweaver integration performance improvements
Development Dashboard has been removed, as it didn't provide a clear useful, ongoing benefit. The information present in the development dashboard has been integrated into our new Help & Support section.
Payment gateway settings - for more privacy and data protection, we have updated the Payment Gateway configuration screens to obfuscate the sensitive login information. Fields that have been obfuscated are now requiring confirmation.
Report abuse badge on trial sites - for compliance reasons, a "Report Abuse" link has been added to the front-end of all trial sites of free partners that don't have any paid sites. When they click the Report Abuse link, site visitors are redirected to a form submission page on businesscatalyst.com site.
Issues fixed by May release
Issues 3051303, 3168786 - Workflow notifications - Fixed a problem preventing workflow notifications emails from being sent.(see get satisfaction forum discussion)
Issue 3164074 - Fixed a bug causing the lightbox gallery created from Muse to be displayed behind page elements
Issue 3162810 - Fixed a bug in rendering engine to prevent content placed between body and head tags being incorrectly moved inside the body tag
Issue 3166610 - Fixed a broken link to Partner Portal in Internet Explorer
Issue 3175003 - Fixed an issue that caused an incorrect price display for the Year One-Off Setup Fee when upgrading a site from Admin using CB
Issue 2567278 - Fixed a bug causing site replication to ignore product attributes
Issue 2947989 - CRM passwords are now case sensitive
Issue 2723731 - Removed CSS files from the head section of the Layouts files, when downloaded and opened in Dreamweaver, via the BC extension
Business Catalyst new admin interface updates
Added "Save and Add New" button in Web App Item Add & Edit screens (see get satisfaction forum discussion)
Updated Quick Actions menus to add more actions (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to display deleted items (see get satisfaction forum discussion)
Fixed a display issue on File Manager making top buttons unreachable (see get satisfaction forum discussion)
Fixed the scrollbars in Email Marketing>Campaign>Stats>Bounced Emails reports (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to brake after selecting the current page from the Recent Items menu (see get satisfaction forum discussion)
Replaced the Success notification displayed when selecting Users or Permissions tabs from User Roles with an Warning
Change the action label displayed in User Roles list from View to Edit to match the list pattern from Admin Users
Fixed a missing file JavaScript error occurring when trying to open image manager from product details-> Attributes -> options
Moved System Emails section from Site Setting to Site Manager (see get satisfaction forum discussion)
Updated Domain Management interfaces to close the modal window and refresh the domain list after successfully adding a domain
Fixed an issue preventing the Hyperlink Manager to function properly (see get satisfaction forum discussion)
Updated the confirmation message received after copying a page to match the new workflow and button names
Fixed an issue causing the current screen or section to not be highlighted in the menu
Updated styling on the new dashboard, user management and email accounts interfaces
Updated dashboard reports filters and chart display; made the chart and the filter use the site time zone
Fixed an issue preventing users from inviting new admin users or create new email accounts on Internet Explorer 8
Fixed an issue preventing users from deleting Email Accounts or Admin Users in Internet Explorer 8
Fixed some issues preventing password recovery email from being sent
Removed the alert message displayed when the user or email account limit has been reached
Added localization for the simplified dashboard
Fixed display issues for site limits, domains and user list in the simplified dashboard
Added Custom reports for webBasics plan
Fixed a bug generating a "500:Collection error" on the simplified dashboard when user did not had View users permission
Added TOU checkbox in the email account setup screen
Updated Site Preview link in the dashboard to load the default domain
Fixed an issue in the new File Manager forcing a user to press Undo twice in order to see the change take effect if the code that was previously formatted contained any <"tag" with more than 2 lines
Fixed an issue causing the File Manager editor toolbar to incorrectly render if page URL path is longer than certain value; starting with this release, the site URL is trimmed
Fixed an issue causing the invite users to be displayed as [object Object] in dashboard and admin user list
Fixed a bug in the new admin causing the interface to become unresponsive when using the browser Back button
Fixed an issue in the new File Manager causing "Save Draft" button to publish the default page template instead of creating a draft version
Fixed a broken invite link issue in the Email Account invite email
Updated loading indicators in File Manager and Email Accounts screens
What's next
The first item on the what's next list might not be news for many of you, but it's definitely one of the most important milestones this year. The Creative Cloud launch is just around the corner, and Business Catalyst is playing an important role in that, as the publishing platform for Adobe® Muse and Dreamweaver. This launch will capture all our attention within the next weeks as we want it to be our best ever.
We'll start our next development cycle on May 15th, while the next Business Catalyst release is going to be pushed live in mid June. That being said, the following items are already on our launch plan for the next release and a few more will join the list. Please expect an update on our 2012 plans around mid May.
HTTP throttling – all page load and API calls to BC will be protected against attacks, this might trigger problems for API heavy sites. We are looking into enabling this update along with our June release, and will help make sure that a reasonable number of requests will be accepted from the same computer per minute.
Automatic site deletion - Starting with the June release, we are going to start automatically delete expired trial sites and canceled sites. Customers will be notified twice before we are going to proceed with deleting the sites.
Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

I'm unable to open up Lightroom 5, I get this message in a pop up box: "Lightroom encountered an error when reading from it's preview cache and needs to quit" Underneath that is "Lightroom will attempt to fix this problem the next time when it launches."

I'm unable to open up Lightroom 5, I get this message in a pop up box: "Lightroom encountered an error when reading from it's preview cache and needs to quit" Underneath that is "Lightroom will attempt to fix this problem the next time when it launches." It hasn't, what should I do? Thanks Shawn (Irish Se7en) .

Can you try to rename (not delete!) the folder named "YOUR_CATALOG_NAME Previews.lrdata" and restart Lightroom?

When I attempt to open lightroom I recive this message: [ Lightroom encountered an error whenreading from itspreviw cache and needs to quit.Lightroom will atempt to fix this problem next time it launches.] I did this a few times but no resoulve

When I attempt to open lightroom I recive this message: [ Lightroom encountered an error whenreading from itspreviw cache and needs to quit.Lightroom will atempt to fix this problem next time it launches.] I did this a few times but no resoulve

It isn't a file, it's a folder. It will have the same name as your catalog, but will have the extension data. It will be in the same folder along with your catalog. If you need to use the search feature to search for *.lrdata.

Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches"."

Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches"."Help
Please

Stan Blumberg wrote:
I have deleted the file but the message persists even after restarting the computer....any advice??...I am using LR 5
You don't delete a file, you have to delete a folder. Is that what you did?
If you deleted the folder specified above, and you still get the message, then it's the wrong folder. Use your operating system's search function and find ALL folders on ALL disks whose name ends with Previews.LRDATA, delete each one found, and then try opening Lightroom.

I have a question about Lightroom 5... I used it last night, I go to get on it today and its will not open. I have an error msg "Lightroom encountered an error when reading from its preview cache and needs to quit" Lightroom will attempt to fix the proble

I have a question about Lightroom 5... I used it last night, I go to get on it today and its will not open. I have an error msg "Lightroom encountered an error when reading from its preview cache and needs to quit" Lightroom will attempt to fix the problem when reopened

https://forums.adobe.com/message/6219922#6219922
See if the issue in the thread above helps you to solve your problem.

When I tried to open Lightroom 5.4 today I got a msg that says "Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it lauches". What do I do? I get the msg each ti

"Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it lauches". What do I do? I get the msg each time I try to open it.

It isn't a file, it's a folder. It will have the same name as your catalog, but will have the extension data. It will be in the same folder along with your catalog. If you need to use the search feature to search for *.lrdata.

Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem next time it launches. " But it doesn't fix it!

I get the following window on loading Lightroom 5.7 -
Lightroom encountered an error when reading from its preview cache and needs to quit.
Lightroom will attempt to fix this problem next time it launches.
I have tried several restarts, without success. Also reinstalled Lightroom; no joy
Any suggestions?

Using your system browser (Windows Explorer or Finder), open the folder that contains your catalog. In Windows it is in your pictures folder and then in a Lightroom folder. Inside of the Lightroom folder you will find another folder that has the extension .lrdata. It will have the same name as your catalog except for the extension. You need to delete that folder, and then start Lightroom again. Lightroom will generate a new previews folder, and you should be back in business.

I have the following problem: Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempts to fix the problem the next time it launches.

I launch and relaunch and the same message appears over and over.
Should I uninstall and then re-install Lightroom? Would this fix the problem?

Thanks Jim.
I will give it a try.
My "Lightroom 5 Catalog Previews.lrdata" folder is 12.3 GB in size, so the rebuild will take lots of time...right?
I'll let you know how it goes.
Ciao.
Michel

Lightroom 5.3 bug fixes.

Similar Messages

Maybe you are looking for