Closed ruippeixotog closed 2 years ago
Hi @mertkahyaoglu, can you take a look at this and evaluate if it's an easy fix? I don't mind giving it a try if you provide me some code pointers. Thanks!
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
The bug is still there and I can't think of anything else to add to the issue.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
No changes here.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
The problem still occurs.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
Description:
/admin/collections/:collection:
endpoint in the frontend stops working when a{% link .. %}
to a bad path is saved during file editing.Tell us a bit about yourself:
Steps to reproduce:
{% link path-to-non-existing-file.md %}
) in a collection;/admin/collections/:collection:
.I expected the following:
jekyll-admin's file browser and editor should still work, allowing me to fix the mistake I did.
But got the following, instead:
An error "Could not fetch the entries" occurs.
Other details:
This happens often when I'm writing links to another post and I happen to have a typo in the URL. Once this happens jekyll-admin stops working for file editing and the only solution is to edit the file manually to fix the error.