As on the screenshot, a lot of hooks are grey and I don't know what the problem is. I don't get the problem for Vue 2 but for Vue 3.
Can anyone tell me what is the problem?
Known issue, please follow WEB-38671 and linked tickets for updates
I can only suggest suppressing the inspection per instructions in help
Related
I have been using the Boot build tool with Hoplon and a Castra backend for a bit but recently have come across a glitch that I don't quite seem to understand. It happens across all my Hoplon projects often. The problem seems to be that when I go to localhost:8000 in the browser sometimes it displays the CSS that is written in 'app.css' correctly and sometimes it doesn't. On top of that sometimes it displays the background images and sometimes it doesn't. I mean in the browser.
I have tried debugging the error for a very long time and have found some ways of getting both loading but not consistently. Sometimes if I edit the hLisp page and save it loads the CSS and Background Images but sometimes that doesn't work. Another way is to edit the app.css file and save. Both are somewhat unreliable.
Any help would be greatly appreciated.
Cheers
I figured out what was causing the error.
(link :href "app.css" ...
Should be replaced by
(link :href "public/app.css" ...
Cheers
Suddenly all ribbons are not coming in Sitecore 8 one of my project.
For example If I am going in publish menu I cannot see any option there.
To solve this issue, I have updated all three folders and config file "sitecore,sitecore_modules,sitecore files & web.config" but still ribbons are not coming for me.
Please assist me what can be solution for this issue.
Thanks all for your effort. I just copied fresh "Content Editor.js" in Content Manger folder and my problem solved.
I believe your ribbons are just collapsed (not expanded). To expand them back there is a little check on the right hand side of the screen. Check the screenshot for reference
I also have same problem and this issue usually coming by difference the version sitecore when you want to integrate with your solution. Try with another sitecore (sitecore,sitecore_modules,sitecore files) version that it
On XE18 non approved glassware in testing no longer display their icons. I've compared the manifests of approved apps to mine and not identified any difference.
Has anyone encountered this and found a solution?
As mentioned in the comments and by EntryLevelDev, the OTA update XE19.1 has pushed out a fix to this bug.
This issue is fixed on XE19.1.
Just for reference, info is here as mentioned in comments.
Cheers!
I followed this tutorial to build a component. Everything works as expected. Now I am confused on how to add an edit feature to the frontend. A uses (with appropriate rights) should be able to click an edit link and edit the data displayed by the component as well as add new data. Just like in the backend.
I have the feeling that I miss something obvious, but I couldn't get my code to work. I thouhgt, I could just replicate the backend code, but with no success.
Is there a tutorial or other hint you could give me?
Thanks
Sascha
I was right: I missed something obvious, because it's all there.
Look at this tutorial. It guides you through the process of integrating an editor to the frontend. But it also shows
how to display an edit form
and
save the data.
Best regards
Sascha
Having a problem with a spinner actually spinning while ember.js is doing it's thing. I have a very generic jsfiddle example that illustrates the issue:
http://jsfiddle.net/h4ZcZ/2/
I assume there has to be a simple way to make this work as expected, but I am not finding it. I have tried using a JavaScript/CSS implementation of a spinner (spin.js) with the same results. I saw some stuff indicating this was typically an IE issue, but that is not the case here. This happens on all browser on Windows and i have tested on Mac Safari as well.
The problem is your for loop--you're basically locking up the thread. I would use timeouts and chunk up the work to be done to give other processing needs on the page the ability to execute.
As far as root cause, #ChristopherSwasey is correct. I asked a few other Ember developers about this. No solution, but two interesting thoughts that might help:
1) One developer reported that he has run into this problem and gotten around it by making sure the animated gif started before the long javascript execution.
2) Another developer suggested that using a virtualized list is the right path, so that only visible nodes are rendered. However, I'm afraid I don't know of an open source Ember virtualized list class yet.
Hope that helps.