Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

component folder empty in crx

doriguetto
Level 2
Level 2

Hi, guys

My component folder is missing on CRXDE Lite but i can see/navigate the component folder in Content Explorer. also, all components are working on sidekick and existing pages. My project is maven based and i use command line to deploy in CQ5. In addition i already checked the maven POMs and content/dialogs and didnt find any inconsistence. Does anyone have any clue what may be the problem? 

1 Accepted Solution
Paul_McMahon
Correct answer by
Community Advisor
Community Advisor

The only reason I can think of that you would see differences between CRXDE Lite and Content Explorer was if you were logged into them as different users. Are you sure you are logged in as the same user? 

The only other possibility is some sort error occurring when you browse in CRXDE Lite. Have you tried entering the path to your component in the search bar below the Save All all button in CRXDE Lite. It would be interesting to see if that generated an error message. You might also try tailing error.log which you try to navigate to the component, as well as checking your browser's JavaScript error console for any clues. 

View solution in original post

1 Reply
Paul_McMahon
Correct answer by
Community Advisor
Community Advisor

The only reason I can think of that you would see differences between CRXDE Lite and Content Explorer was if you were logged into them as different users. Are you sure you are logged in as the same user? 

The only other possibility is some sort error occurring when you browse in CRXDE Lite. Have you tried entering the path to your component in the search bar below the Save All all button in CRXDE Lite. It would be interesting to see if that generated an error message. You might also try tailing error.log which you try to navigate to the component, as well as checking your browser's JavaScript error console for any clues. 

View solution in original post