Hot answers tagged

9

You would have to make CSS updates through a GUI extension besides using the new line (\n) in your exception message. In your event system exception, you will be using the new line like this: throw new Exception("Some text before new line.\nSome text after new line."); In the GUI extension, set the CSS white-space property to pre-wrap in the div element of ...


6

You could impersonate that specific user in your code and then request all publications as them. This should give you the complete list that they're able to access. Alternatively, you could get every publication and then iterate over them to determine whether the user (or a group that they're a member of) has any rights on that publication.


6

As Neil and Mark have noted, what you are looking for is a GUI extension extending the FormatArea.js and three other JavaScript and ASPX files: %Tridion Home%\Web\WebUI\Core\Controls\FormatArea\FormatArea.js %Tridion Home%\Web\WebUI\Editors\Base\Views\Popups\Link\Link.aspx %Tridion Home%\Web\WebUI\Editors\Base\Views\Popups\Link\Link.js %Tridion Home%\Web\...


4

As far as I know, the state store DB contains the state of a publish transaction during that transaction, and this data is/can be removed once that transaction has successfully finished. This means that indeed, you can disable publishing, make sure all publish transactions are finished, set up a new state store db and reconfigure your microservices to point ...


2

There is no OOTB way to add options into the existing dialog. As Neil notes, if you try to extend the current pop-up you will have challenges extending the formatarea.js as there's no supported extension point to that file. Take into consideration also this needs to work with the xdm {cross domain methods} object for cross-domain scripting if you're using ...


2

Looking at the error, it seems that there is a blueprint conflict. The error actually tells you which items is the conflicting one: tcm:373-156169-1024. It seems that such keyword exists at a lower level (or higher) level in the blueprint from where the script is attempting to create it. Make sure that the level of the blueprint you are importing items ...


2

Standard DXA TBBs do publish binaries (you can check in Template Builder, in the CME preview or by intercepting a Transport Package). However, DXA assumes that your Deployer is configured to deploy binaries to the CD Content Store (aka Broker Database). If you say you don’t see anything in the DB, I guess that is your problem.


2

Try following to troubleshooting. First, check that your website domain URL mapping URLs exist in the discovery database or not? by using postman http://localhost:8082/discovery.svc/PublicationMappings, in case if you looking for how to access postman to explore SDL microservices Could be Discovery Service out-of-sync with Topology Manager then you can ...


1

When I resolved another issue this problem was resolved as well. It seams my images was published all the time in original format. But when I saw that the image variants was missing in the website I thought the renditions should be created by TBBs at publishing time. Now I believe they are generated at runtime. For some reason they couldn't be generated due ...


1

It seems that the DXA 2.2 resolver is built against SDL Tridion Sites 9.0 API, so it can’t be loaded on a SDL Web 8.5 system. Frankly, I’m flabbergasted, because I’m quite sure that DXA 2.2 has been tested against SDL Web 8.5. This should be reported as a DXA 2.2 defect. It should be possible to work around this issue by putting assembly binding redirects ...


Only top voted, non community-wiki answers of a minimum length are eligible