-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the Markdown editor's implicit dependency on Media #17348
Comments
Expect Behaviour |
What do you see in the browser and OC logs? Is the screenshot with the package references that of your web app's? |
Screenshot with "Edit MDT2" is what I am seeing where was expecting the screenshot with "Edit MDT" Package references are my project references (just following template :) ) Log is not providing clues (thank you for the "media" error feedback). |
I mean, the screenshot with the package references, is that from the root web app of your solution? Because if it is, then you don't need any other The browser log shows that the editor is not loaded, most possibly because its JS is not loaded. Do you see a 404 for that in the log there too? Please share the full browser log. |
how do I grab the "full browser log" :) |
Sorry, more precise is that please share a HAR file, which will include all data about the browser's network communication. See e.g. this guide: https://support.zendesk.com/hc/en-us/articles/4408828867098-Generating-a-HAR-file-for-troubleshooting |
Zipped HAR file attached, I think :) |
The problem is that Do you perhaps have the Media feature turned off? There seems to be an implicit dependency between the Markdown editor and the Media module. |
Hooray - thank you!!!!!!! That's it - Media module needs to be enabled. Maybe make Markdown dependent on Media via manifest file in Markdown module? |
Great! Yep, that's an issue. There are multiple problems:
|
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
1 similar comment
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
@Piedone what's the action needed here? |
See above. |
See #17348 (comment) below.
Describe the bug
I have created a ContentType that uses a MarkdownBodyPart. When I edit it using the "Content Items" list in Contents module the WYSIWG editor does not initiated. I can edit the content and it rendered correctly when displaed. It is just the editor in the Edit view that is the issue.
Only occurs when site hosted on Azure Web App (windows). DOES NOT occur when run locally in debug mode
Orchard Core version
OC 2.1.3
To Reproduce
Azure Hosted WebApp
Using OC 2.1.3
Content Type Definition
Go to Dashboard - ContentItems
Create new instance of type with MarkdownBodyPart
Issue - editor not rendering.
![image](https://private-user-images.githubusercontent.com/18185015/402850569-8039372f-dfa3-455f-a8c0-4567e8da6873.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNTQzNjcsIm5iZiI6MTczOTM1NDA2NywicGF0aCI6Ii8xODE4NTAxNS80MDI4NTA1NjktODAzOTM3MmYtZGZhMy00NTVmLWE4YzAtNDU2N2U4ZGE2ODczLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA5NTQyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJlOWEyYTAyYTdjNmRjNDAxZmZhMTQ2ODkzNWY1OGJiYTJiMzU4YTc2Yzk4MDQxYjljODQ1YWJkYzQxY2M1ZDcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.5MG1-ND8WDfSiBPEwGY0aemU3TKzUprQp1TCbSXVeYA)
Note: Issue does not occuring when I run locally.
Expected behavior
Logs and screenshots
The text was updated successfully, but these errors were encountered: