If the author instance tries to publish content to a public instance without a valid license, you will see the following in the log: 

To resolve this issue, see the section on updating a key on the  License page. 

See also Publishing and activation.

In some cases, your license is valid but you have different Magnolia versions running in the Author and Public instances. 

In this scenario, check the value of the /server/filters/multipartRequest/@enabled parameter. It must be set to true.

In some circumstances, you may need to set the parameter to false, for example to get REST calls to work with attachments. If this applies to your case, use a bypass:

<sv:node xmlns:sv="http://www.jcp.org/jcr/sv/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" sv:name="skipRestCall">
  <sv:property sv:name="jcr:primaryType" sv:type="Name">
  <sv:property sv:name="class" sv:type="String">
  <sv:property sv:name="pattern" sv:type="String">
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels

1 Comment

  1. I think this can also happen if you try and publish to an instance which does not have the transactional modules installed. You could have a valid license but incompatibility between regular and transactional activation.