Hello,

I am happy, because I have well identified where the problem comes from !!!
As soon as I put a value for the cache in the module (5 sec or 4800 sec or 172400 sec - the values I tested), I have this problem of layout !! With the cache set to 0, no more problem...

Up to you now... ;-) What can I do ? Can someone reproduce the problem with DNN 4.3.7 ?? My test website is on 4.4.0 and I do not have this behavior.

 To answer my previous questions:
When I put ONE repository module into my webpage, I have to define the path for files (Folder for Approved Files). Once I have done this and uploaded one file into the module, I do not have this setting anymore.
==> IS IT NORMAL ??? <==
I had this problem because ADMIN do not have the same privilege than HOST. ADMIN can not set the "folder for Approved Files". To my opinion, this is not normal.

If I create a new module, I did not have this setting neither (it means that all files that I upload into another page and another module must be in the same path).
==> IS IT NORMAL ?? <==
Same than before, it was linked to the fact that I used the second time the ADMIN account... Instead of HOST account.

Finally, when I check my database, table dbo.grmRepositoryObjects, I still see an old entry (itemID linked to an old deleted module).
==> IS IT NORMAL ??? <==
For this one, I have still no idea.

For the first two questions, I would be very interested if someone can test and keep me informed ? Is it normal than ADMIN can not modify and access this setting ??

DV FX

Thanks mikeh for this answer. For your information, I have emptied the recycle bin, it does not change anything in the database (but this is a detail). Do you have an idea for my "main problem" (see first text message with screen capture). I.E. the problem with the cache setting to something different than zero, bringing "strange behavior in the presentation of the page"... :-(

I have also deleted again the module, and clean up the database like that:

drop table dbo.grmRepositoryAttributes;
drop table dbo.grmRepositoryAttributeValues;
drop table dbo.grmRepositoryCategories;
drop table dbo.grmRepositoryComments;
drop table dbo.grmRepositoryObjectCategories;
drop table dbo.grmRepositoryObjects;
drop table dbo.grmRepositoryObjectValues;

drop procedure dbo.grmAddRepositoryAttributes;
drop procedure dbo.grmAddRepositoryAttributeValues;
drop procedure dbo.grmAddRepositoryCategory;
drop procedure dbo.grmAddRepositoryComment;
drop procedure dbo.grmAddRepositoryObject;
drop procedure dbo.grmAddRepositoryObjectCategories;
drop procedure dbo.grmAddRepositoryObjectValues;
drop procedure dbo.grmApproveRepositoryObject;
drop procedure dbo.grmChangeRepositoryModuleDefId;
drop procedure dbo.grmDeleteRepositoryAttributes;
drop procedure dbo.grmDeleteRepositoryAttributeValues;
drop procedure dbo.grmDeleteRepositoryCategory;
drop procedure dbo.grmDeleteRepositoryComment;
drop procedure dbo.grmDeleteRepositoryModuleDefId;
drop procedure dbo.grmDeleteRepositoryObject;
drop procedure dbo.grmDeleteRepositoryObjectCategories;
drop procedure dbo.grmDeleteRepositoryObjectValues;
drop procedure dbo.grmGetRepositoryAttributes;
drop procedure dbo.grmGetRepositoryAttributeValues;
drop procedure dbo.grmGetRepositoryCategories;
drop procedure dbo.grmGetRepositoryComments;
drop procedure dbo.grmGetRepositoryModules;
drop procedure dbo.grmGetRepositoryObjectCategories;
drop procedure dbo.grmGetRepositoryObjects;
drop procedure dbo.grmGetRepositoryObjectValues;
drop procedure dbo.grmGetSingleRepositoryAttributes;
drop procedure dbo.grmGetSingleRepositoryAttributeValues;
drop procedure dbo.grmGetSingleRepositoryCategory;
drop procedure dbo.grmGetSingleRepositoryComment;
drop procedure dbo.grmGetSingleRepositoryObject;
drop procedure dbo.grmGetSingleRepositoryObjectCategories;
drop procedure dbo.grmGetSingleRepositoryObjectValues;
drop procedure dbo.grmUpdateRepositoryAttributes;
drop procedure dbo.grmUpdateRepositoryAttributeValues;
drop procedure dbo.grmUpdateRepositoryCategory;
drop procedure dbo.grmUpdateRepositoryClicks;
drop procedure dbo.grmUpdateRepositoryComment;
drop procedure dbo.grmUpdateRepositoryObject;
drop procedure dbo.grmUpdateRepositoryObjectCategories;
drop procedure dbo.grmUpdateRepositoryObjectValues;
drop procedure dbo.grmUpdateRepositoryRating;

I have also deleted the following folders:
Repository folder in DesktopModules
Portals/0/Repository + Repositorynoimage.jpg

DesktopModules\Dashboard\
bin\DotNetNuke.Modules.Repository.dll
bin\DotNetNuke.Modules.Repository.SqlDataProvider.dll

Because the uninstall does not work well. With the new installation, I still have this problem of cache. Can you test it and keep me informed (on DNN 4.3.7) ?

DV

Ok, this is definitely CONFIRMED (for me, but I would like someone confirmation) !  I have just mounted a new test web site DNN 4.3.7 from scratch, and I included a Repository module, with a cache value. As soon as I do so (cache value), when you logout, the strange behavior appears !

Could one of you confirm this with 4.3.7 please ?

DV