So we searched the episerver database and ended up with some questions.
1. None of the composer blocks got any data saved in the tblPageLanguageSetting table, is this needed?
2, What are the differences concearning composer blocks, global blocks regarding changes in the database.
3. Which attributes are needed in the db in order for the blocks to be saved?
We are seeing the same timeouts, when copying a layout function containing many content functions from the clipboard. Its around 20 seconds per content function, which seems very slow.
Before upgrade to R2, copying was smooth.
SQL Profiler shows a stored procedure "composerCompleteImport" spending many seconds JOIN'ing all properties, pages and pagetypes while doing a lot of string-comparison. This time will increase with the amount of content in your EPiServer database.
I had the same problem with timeouts when creating globals blocks after upgrading to R2. The procedure "composerCompleteImport" took so long that I got sql timout exceptions.
I got a script from the episerversupport that solved it. Ask the support for this script: composerfix_bug78100_20120417.sql
Getting timeout error when saving globalblocks after an upgrade from cms 6 + composer 4 to cms 6R2 + Composer 4R2. it did work as it should before the upgrade. And how is the language handled within the global blocks? In other words how can i set language to a specific global block.
We also noticed a programming error when pressing the save as button in order to get into global block options in order to save it the Categories panel is missing text due to missing wrongfully named element in code. The code states Kategorier when it should be Categories. Easy enough to fix but it shouldnt be there in the first place...
Error log regarding first problem: