Since introducing a dedicated database for a publishing target in Experience Edge Connector 20.0, a fake experienceedge database has been added in the App_Config\Modules\ExperienceEdgeConnector\ExperienceEdgeConnector.config file. This article describes different known issues related to the experienceedge database and provides some solutions.
The issues mentioned affect Experience Edge Connector starting from 20.0.
Note that, for the most part, these issues should be simply noted when adding a custom code that interacts with databases.
Any operation with the experienceedge database returns a null or empty result.
For example:
var db = BaseFactory.GetDatabase("experienceedge");
var item = db.GetItem(...); //item is null
It is recommended that you not perform any operation with this experienceedge database.
The publish button is always enabled in the Experience Editor user interface (UI).
The issue can be safely ignored.
The PublishHelper cannot be used for the experienceedge database as it requires the PublishOption object which requires a non-fake target database.
As a solution, use the PublishManager class for any publishing operation in your custom code instead of the PublishHelper class.