Raffael Meyer

We can do without the backports, if this is too breaking.

@sagarvora I've reduced the scope of this PR. Now it only applies to printed filters, which was my original problem.

Apparently this was for a formerly planned feature that was never finished.

Also, tests are passing on my local 🤔

Investigation so far: `Comment.reference_doctype` gets reset from `"Blog Post"` to `None` due to this line: https://github.com/frappe/frappe/blame/c441be55e60abbf606396543fa3b0af67ef301f0/frappe/model/base_document.py#L850 `get_invalid_links` has way too many responsibilities and it's not clear to me yet, why...

It seems like the changes in this PR already improve the situation. However, I found the following remaining issues, in case you wish to fix theses as well: - After...

A different trade-off between standardization and flexibility. This doctype tries to model a german employment contract while **Job Offer** is just a set of arbitrary terms.

Let's plan this for `version-16`, maybe contribute to hrms.

Not all apps have a presence in the workspaces. Please use the navbar to search for "Sendcloud" or "LetMeShip".

Sorry, I meant the navbar of ERPNext, not of your browser.