Workflowengine "The given regular expression is invalid" #23666

Activity

1. R0Wi

   added

   bug

   0. Needs triagePending check for reproducibility or if it fits our roadmapPending check for reproducibility or if it fits our roadmap

   on Oct 24, 2020
2. kesselb commented on Oct 24, 2020

   

   kesselb

   on Oct 24, 2020

   Contributor

   More actions

   Thanks for reporting 👍 I see the same issue on Nextcloud 19.

   cc @juliushaertl @blizzz as 'httpd/unix-directory' is not a pattern they cannot use matches as operator. We should probably hide operators which are not compatible to each other. We have the same issue the other way around for File MIME type is Office Documents.

   👍React with 👍1Reacted by Robin Windey
3. wiswedel

   added

   feature: workflows

   on Feb 2, 2021
4. R0Wi commented on Feb 25, 2021

   

   R0Wi

   on Feb 25, 2021

   MemberAuthor

   More actions

   Hi since the number of reported issues at the workflow_ocr app regarding this problem is increasing i'd kindly like to ask what are the plans for this? If we like to implement #23666 (comment) i can try to do this if you're willing to accept my PR ? 😃

   cc @juliushaertl @blizzz @kesselb

   👍React with 👍1Reacted by stefanp2021
5. kesselb commented on Feb 25, 2021

   

   kesselb

   on Feb 25, 2021

   Contributor

   More actions

   can try to do this if you're willing to accept my PR

   Cool 👍

   since the number of reported issues at the workflow_ocr app

   A pinned FAQ issue might help with that. At least here at nextcloud/server it helps a bit.
6. R0Wi commented on Feb 25, 2021

   

   R0Wi

   on Feb 25, 2021

   MemberAuthor

   More actions

   A pinned FAQ issue might help with that. At least here at nextcloud/server it helps a bit.

   Thanks for the hint, will give it a try 😄

   So basically i'd implement it the following way (given that the first column is set to File MIME type):

   • The entries of third column (containing the the filetype) are filtered with respect to the second columns choice (comparator)
   • If the user sets the comparator to is or is not the filetypes Folder, PDF Documents and Custom mimetype will be shown in the third column
   • If the user sets the comparator to matches or does not match the regex based types Images and Office documents will be shown in the third column

   Would that be the way to go @kesselb ?
7. blizzz commented on Feb 25, 2021

   

   blizzz

   on Feb 25, 2021

   Member

   More actions

   @R0Wi generally that sounds good to me.

   On a second thought, it is quite technical for the end user. An admin might now about regex's and stuff, but for the average user "is (not)" or "matches (not)" or the meaning of it is black magic. The best way would be to eliminate the differences (only keep is _(not)) and figure out what is desired by testing the third columns value.

   That would be a bigger change however, and not backportable. This is an advantage of your suggestion, so let's go with it.

   Changing the UI more radically (it has effects on the backend bits, too) could be something for 22.
8. szaimen commented on Jun 23, 2021

   

   szaimen

   on Jun 23, 2021

   Contributor

   More actions

   I suppose this is still valid on NC21.0.2?
9. szaimen

   added

   needs info

   on Jun 23, 2021
10. R0Wi commented on Jun 24, 2021

    

    R0Wi

    on Jun 24, 2021

    MemberAuthor

    More actions

    AFAIK unfortunately yes. Did not manage to create a PR, yet 😢
11. szaimen

    added

    1. to developAccepted and waiting to be taken care ofAccepted and waiting to be taken care of

    and removed

    0. Needs triagePending check for reproducibility or if it fits our roadmapPending check for reproducibility or if it fits our roadmap

    needs info

    on Jun 24, 2021
12. FernandoMarques-Santos commented on Jul 29, 2021

    

    FernandoMarques-Santos

    on Jul 29, 2021

    More actions

    NC 21.0.3 Workflow OCR 1.21.1, the problem still persists.

    The only way to deal with this, for now, is to remove the other conditional, in my case, it was file MIME = pdf.
    As I wanted it to ocr just files created/modified with 2ocr somewhere in its name (insert /2ocr/i in the box), it is usable for now.
13. 4 remaining items

    Load more
14. szaimen

    added

    0. Needs triagePending check for reproducibility or if it fits our roadmapPending check for reproducibility or if it fits our roadmap

    on Jan 23, 2023
15. github-cli commented on Jan 23, 2023

    

    github-cli

    on Jan 23, 2023

    More actions

    I dont have an issue with this anymore in general as after reading all this back when I had the issue I just know what I need to click and what that error actually means...
    However I would love to help as far as I can...
    I just tested this on 25.0.3 and selected "matches" PDF and it tells me that the regular expression is invalid.
16. szaimen

    added

    25-feedback

    and removed

    needs info

    on Jan 23, 2023
17. rotdrop commented on Mar 2, 2023

    

    rotdrop

    on Mar 2, 2023

    Last edited by rotdrop

    Contributor

    More actions

    Actually, when you choose "custom MIME type" you are facing a similar error. But this is a bogus user-interface: the placeholder suggests that you just can add "e.g. http/unix-directory". However, the placeholder suggestion is wrong, you need to enter a full-fledged regular expression, i.e. http/unix-directory does not work, but something like |http/unix-directory|.

    I have no problems with entering a regular expression, but neither the placeholder nor the cryptic error message The given regular expression is invalid are of any help for directing the struggling user into the right direction.

    I experienced this with a up-to-date v25 NC. Screenshots are appended

    
    
    

    👍React with 👍1Reacted by B-Dawg
18. Nils160988 commented on Nov 13, 2023

    

    Nils160988

    on Nov 13, 2023

    Contributor

    More actions

    Still valid for NC 27.1.3
19. R0Wi

    added 2 commits that reference this issue on Jan 18, 2025

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 52fa172 is merged into the 'master' branch.

    52fa172

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 21d167a is merged into the 'master' branch.

    21d167a
20. R0Wi

    added a commit that references this issue on Apr 26, 2025

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit c6f52e1 is merged into the 'master' branch.

    c6f52e1
21. R0Wi

    added a commit that references this issue on Jun 30, 2025

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 4420a2e is merged into the 'master' branch.

    4420a2e
22. R0Wi

    added 5 commits that reference this issue on Dec 6, 2025

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 3b2b368 is merged into the 'master' branch.

    3b2b368

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 53ef912 is merged into the 'master' branch.

    53ef912

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 7bd2d6a is merged into the 'master' branch.

    7bd2d6a

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 0d320d3 is merged into the 'master' branch.

    0d320d3

    fix: restrict mime type list depending on check operator

    ...

    This issue will close once commit 3249ee2 is merged into the 'master' branch.

    3249ee2