Skip to content
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

App is not compatible with Nextcloud's "Text" app #116

Open
zerknorscht opened this issue Mar 6, 2020 · 10 comments
Open

App is not compatible with Nextcloud's "Text" app #116

zerknorscht opened this issue Mar 6, 2020 · 10 comments

Comments

@zerknorscht
Copy link

As Text is the default Editor for markdown files in Nextcloud 18, no other Editor is working out of the Box and the Text App is breaking the fomatting of the yaml headers, wich leads to broken pages I cannot figure out, how to use cms_pico without editing it through an external editor.
Maybe I am missing something here, but isn't the point of having a cms integration in NC being able to edit it from WITHIN Nextcloud?

I cannot get it to work right for me and I think it is a pretty big Issue....
The real Problem seems to be about the Text-App, not about pico, but maybe some devs from both apps could get in touch wich each other (if it's not being done allready)
I think I saw an Issue about this in the Text App, but from their perspective it seems to be a minor issue... from the usability of cms_pico however it seems to be rather major, right?

@PhrozenByte
Copy link
Collaborator

PhrozenByte commented Mar 6, 2020

This is indeed an issue with Nextcloud's Text app, not with Pico CMS for Nextcloud. The issue is known. See nextcloud/text#593 and nextcloud/text#145, also see related nextcloud/text#123, nextcloud/text#439 and nextcloud/text#2218.

@Subnet-Masked
Copy link

Just a bump that the title might benefit from being more general. This issue affects all versions of Nextcloud from 18-21.0.2 that have the new version of the text app, not just NC 18

@PhrozenByte PhrozenByte changed the title App is not compatible with NC18 / files_text App is not compatible with Nextcloud's "Text" app May 30, 2021
@nooblag
Copy link

nooblag commented Jun 29, 2021

I agree. In the meantime, is there a way you could associate Pico's files to open with Plain Text Editor or a Markdown editor that doesn't break things in the meantime? We still have this issue on Nextcloud 21.0.2.

@PhrozenByte
Copy link
Collaborator

PhrozenByte commented Jun 29, 2021

You can install Nextcloud's Markdown editor to associate .md files with this editor instead, see https://github.com/icewind1991/files_markdown#behaviors on how to open these files with Markdown editor instead. The easiest solution is to disable Nextcloud's Text app.

@nooblag
Copy link

nooblag commented Jun 29, 2021

Thanks for that. Yes, we could disable the Text app, but we use that as our users seem to prefer that rather than the Markdown app because of the confusing preview interface (your content is shown twice). I think in the absence of a fix either there or here, we'll probably have to resort to the "right click, open with plain text editor" workaround, which isn't the best, but it will do.

@PhrozenByte
Copy link
Collaborator

Unfortunately we can't do anything about this. I'm not sure whether this is caused by how Nextcloud handles file associations, or whether it is caused by the Text app. You might wanna open a feature request on Nextcloud's server repo to implement a "default app" chooser or something?

@asereq
Copy link

asereq commented May 7, 2023

I think this was solved few months ago when nextcloud/text#145 was fixed.

@joshtrichards
Copy link
Member

Has anyone tested this more recently, with newer versions of Nextcloud and the Text app, since both nextcloud/text#2751 and
nextcloud/text#3460 were merged?

@nooblag

This comment was marked as off-topic.

@PhrozenByte
Copy link
Collaborator

Has anyone tested this more recently, with newer versions of Nextcloud and the Text app, since both nextcloud/text#2751 and
nextcloud/text#3460 were merged?

There were indeed very, very major improvements towards compatibility. Some rather small issues remain (some of which I'd say don't matter much in practice), thus we should keep this issue open, just to keep track of that as of now rather minor fact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants