I've been playing around with Typo3 Neos. So I've installed it according to this tutorial, except i didnt import the demo Package.
Just to be safe, I deactivated and deleted the TYPO3.NeosDemoTypo3Org package, before flushing the cache. So when i log into the backend, there is the "print" button, in the preview part of the menu, and there are custom nodes which are defined in the demo package (which i deactivated and deleted). It isnt hard to imagine, when i try to add these Nodes i receive an error message:
Failed to render element
page<TYPO3.Neos:Page>/
body<TYPO3.TypoScript:Template>/
content/
main<TYPO3.Neos:PrimaryContent>/
default<TYPO3.TypoScript:Matcher>/
element<TYPO3.Neos:ContentCollection>/
itemRenderer<TYPO3.Neos:ContentCase>/
default<TYPO3.TypoScript:Matcher>/
element<TYPO3.NeosDemoTypo3Org:Carousel>
Invalid resource URI "resource://TYPO3.NeosDemoTypo3Org/Private/Templates/NodeTypes/Carousel.html": Package "TYPO3.NeosDemoTypo3Org" is not available. (201402131504259fdc08)
It clearly says there is no Carousel Node (because the package where the carousel should be, was deleted). So here is my Question: Why is this still there?
Make sure you flushed the Cache correctly. In Production context it is
FLOW_CONTEXT=Production ./flow flow:cache:flush --force
But it seems more likely that in your TYPO3 Content Repository, you still have a Carousel content which of course isn't deleted on installing the Demo Package. So have a look at your Node table and check for the node type TYPO3.NeosDemoTypo3Org:Carousel and delete these nodes.
Related
We had some projects deleted in Azure DevOps and we restored them, however all the widgets in the dashboard are broken. Is there a way to recover them or do we have to rebuild?
The dashboard does report across 3 projects, all of which were deleted then restored.
I receive a message about a / in a project title, but the project title I see does not have a /.
I have searched the User Guide and cannot seem to find the answer on this or one that explains the error message.
enter image description here
#wadezhou Cloud service. The error message says 'Widget error 400: The query configuration is invalid or number of work items returned exceeds the size limit.' (link above) I don't believe it is due to work items because I don't believe any work items have been added (these projects are just a proof of concept) and it was working before they were deleted. I have not tried to create a new widget - I will try that and see if it works and let you know. I'm not sure to tell if it's TFVC or git? It is Agile.
Here is a screenshot of the error where it mentions the / (when I go into the query):
error detailing /
When I try to create new widgets on the dashboard one works and one doesn't:
enter image description here
From what I can tell - it seems Git is the default type, and I have not changed it from whatever default would be.
I am trying to upload an image in DAM and workflow (OOTB) gets stuck. following is the error I am getting.
12.07.2018 09:58:27.712 *ERROR* [JobHandler: /etc/workflow/instances/server1/2018-07-11_2/update_asset_923:/content/../../../../../../icon-1.png/jcr:content/renditions/original] com.day.cq.dam.core.impl.AssetImpl addRendition: cannot add new rendition [cq5dam.thumbnail.48.48.png] for asset [/content/dam/____________________________]:
com.adobe.granite.asset.api.AssetException: javax.jcr.version.VersionException: Cannot set property. Node is checked in.
at com.adobe.granite.asset.core.impl.DefaultRenditionHandler.setRendition(DefaultRenditionHandler.java:79)
at com.adobe.granite.asset.core.impl.AssetImpl.setRendition(AssetImpl.java:131)
at com.day.cq.dam.core.impl.AssetImpl.addRendition(AssetImpl.java:490)
at com.day.cq.dam.core.impl.AssetImpl.addRendition(AssetImpl.java:484)
at com.day.cq.dam.core.impl.RenditionMakerImpl$PlanBasedTemplate.apply(RenditionMakerImpl.java:129)
at com.day.cq.dam.core.impl.RenditionMakerImpl.generateRenditions(RenditionMakerImpl.java:184)
at com.day.cq.dam.core.process.CreateThumbnailProcess.execute(CreateThumbnailProcess.java:121)
at com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.execute(CQWorkflowProcessRunner.java:93)
at com.adobe.granite.workflow.core.job.HandlerBase.executeProcess(HandlerBase.java:215)
at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:143)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.startJob(JobQueueImpl.java:395)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl.access$100(JobQueueImpl.java:66)
at org.apache.sling.event.impl.jobs.queues.JobQueueImpl$1.run(JobQueueImpl.java:238)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.jcr.version.VersionException: Cannot set property. Node is checked in.
at org.apache.jackrabbit.oak.jcr.session.NodeImpl$35.checkPreconditions(NodeImpl.java:1330)
at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.prePerform(SessionDelegate.java:606)
After image upload I can see the property set on the asset node is
What can be the possible cause of this.
This is a known product bug affecting AEM 6.0, 6.1 and 6.2.
From official documentation
This is a known product bug CQ-4215298. When a user creates a version
or publishes ("activates") a page that is locked by another user, then
it causes the page to go into an inconsistent state.
Resolution
This issue is fixed in AEM6.3 and AEM6.2 SP1 Cumulative Fix Pack 8.
With or without the fix pack applied, you would have to fix the broken
pages. To fix the pages, follow the steps below:
Go to /crx/explorer/index.jsp and log in as admin user. Open Content
Explorer. Browse to the jcr: content subnode of the broken page. For
example: /content/geometrixx/en/services/jcr:content Go to Versions =>
CheckOut. Go to /sites.html UI and browse to the page and open it for
editing. Unlock the page by clicking the lock icon on the top left.
This is the scenario (CQ5.6). Let's say there is the following node /content/geometrixx/articles, with articles inside of it. In author instance I create a package as a backup of that node. Then I deactivate article1 inside of articles, if I try to access the page I get a 404 page, that is fine. However if I build the backup package again and then replicate it, the deactivated page (article1) is available, that is, I do not get the 404 but instead the article.
Is there a way to replicate a package while preserving deactivated pages? That is, how I avoid re-activation?
Replicating package means that you are replicating every thing available in Package. Which means publish environment will have deactivated pages also. There are several ways to handle it, like:
Simplest way is to add a check in template (as first rule) to see if Env==publish && requested resource ==not activated, if so, return 404 page.
Another way is to create a script to delete all deactivated pages, and run this script on publish after page activation.
Add exclude filters in your package to exclude such pages.
I would recommend to use #1 as this is one time change and will be future proof.
should use treeactivation: http://localhost:4502/etc/replication/treeactivation.html, much safer (since you have 3 options: Only Modified, Only Activated and Ignore Deactivated)
To start, I followed these directions exactly as it's stated: http://dev.day.com/docs/en/cq/5-6/developing/mobile/responsive.html
The problem is, despite all of that, my Devices dropdown on the sidekick in preview mode is empty.
The list works without issue in the Geometrixx Media without issue.
I made sure I set the cq:deviceGroups and the sling:OsgiConfig as required, and also included the simulator.js in the head tags.
Edit: I have found that if I set the resourceType on the root level page to geometrixx-media/components/page, which is their working demo, it works. I have completely removed all jsp and config items from that component page and it still continues to work anyways.
Does anyone know of something that is missing from the documents, and how to fix the issue?
Thanks.
This is what I did to resolve this issue:
I am going to assume your application name is jason-riis
In CRXDE|Lite create a config folder in /apps/jason-riis/
Now create a node of:
TYPE=sling:OsgiConfig
NAME=com.day.cq.wcm.mobile.core.impl.MobileEmulatorProvider-<*alias>
*alias could be anything, I gave my application name. What it does is it will get you a unique PID when you look at it in configuration Manager
If you go to your configuration manager now, you should be able to see two MobileEmulatorProvider config settings.
Add a node property to node you just created:
NAME=mobile.resourceTypes
TYPE=String[] (you have to click multi at the end of the value textbox)
VALUE=jason-riis/components/<*page>
*page is all the components that has sling:resourceSuperType of foundation/components/page and it is a multi array so it should look like this
jason-riis/components/page, jason-riis/components/widepage, jason-riis/components/newspage
I assume you already have the cq:include for simulation in your header. This makes the devices button appear in preview mode.
Last thing is, go to your website root page's jcr:content [/content/jason-riis/jcr:content] and add node property
NAME=cq:deviceGroups
TYPE=String[]
*VALUE=/etc/mobile/groups/touch, /etc/mobile/groups/smart
*If you go to this etc path in CRXDE|Lite; you will see more relevant information in jcr:content node. This will help you in creating your own custom emulator list.
You should be able to see the dropdown now, with options of iPhone and iPad and all. I know AEM docs are frustrating, let me know if there is any confusion.
My hosted app is showing a floating banner with a notice saying “Installation of this item may not work properly.” on its Google Chrome Web Store product page. The app is undiscoverable by searching the Web Store.
What is causing this problem? I find no additional information in the developer dashboard.
If you get this message, it is probable that there really is an error in the manifest or locale files (For example, in my case it was a trailing comma on the locale files).
The process y follow to solve the problem was:
Try to instal the app version you have just submited to the chrome store. When you try to install the app you will probably get a error message thats points you on the track of the problem of your manifest file.
Solved the problem on the app and upload it again. You may get the same error on the developers panel. Two thinghs can be appening:
A) If you've already corrected all errors in the manifest files remenber to publish the changes and what is more important remenber that the publication process may take a few minutes to become effective. The message will disappear after a while if everything is okay. (This explains why is you look on the internet for that problem you find people saying that the message will disappear after a while)
B) If error persist event after the publishing process have been complete finished. You may have not solved all error on the manifest file go back to Step 1
cheers
I had this exact problem. When I tried installing, I got an error message about a missing file.
When I removed my locales directory, everything worked fine.