please stop deleting posts

[jamie]

I was disappointed to see the recent discussion around documentation improvements removed, because the intention behind it was genuinely constructive.

EspoCRM is an extremely capable platform with a strong technical foundation, but one recurring theme throughout years of forum discussions is that many users struggle with the documentation — especially around formulas, hooks, metadata behavior, ORM usage, lifecycle timing, and architectural expectations.

This is not usually because users refuse to read the docs. In many cases, users have read them, but still end up needing clarification through forum threads because:

• important edge cases are undocumented,
• runtime behavior differs from user expectations,
• practical examples are limited,
• or implementation details assume deep framework knowledge.

A lot of the most valuable explanations currently exist only inside scattered forum replies rather than official documentation.

The removed post was not intended as criticism of the enormous amount of work that goes into maintaining EspoCRM. It was simply trying to highlight recurring friction points that appear repeatedly across many years of community discussions.

I also think it is important for communities to leave room for constructive criticism and improvement discussions, even when people disagree with parts of the feedback. Open discussion around user experience, onboarding difficulty, and documentation quality can ultimately strengthen the ecosystem long-term.

Many users making these suggestions are not attacking the project — they are invested in it, building on top of it, and trying to help identify areas where the experience could become even better.

Hopefully conversations like this can remain open in the future, because they often contain valuable insight into the challenges newer developers and integrators face when adopting the platform.

[yuri]

Hi,

The post was a long LLM output. We will keep deleting such posts. It's a normal practice nowadays not to pollute forums with LLM output. We don't need an LLM summary based on just a few posts the LLM found for a particular prompt. It's a slop.

When a 'constructive criticism' is the same from the same user over and over, when it ignores previous answers, it's normal to suppress it.

Criticism like the following:

- Why it's not documented.
- Actually it's documented, here.
- Why isn’t it at the very top?

should not only be deleted, but may also justify a ban.

[jamie]

Hi,

The post was a long LLM output. We will keep deleting such posts. It's a normal practice nowadays not to pollute forums with LLM output. We don't need an LLM summary based on just a few posts the LLM found for a particular prompt. It's a slop.

When a 'constructive criticism' is the same from the same user over and over, when it ignores previous answers, it's normal to suppress it.

Criticism like the following:

- Why it's not documented.
- Actually it's documented, here.
- Why isn’t it at the very top?

should not only be deleted, but may also justify a ban.

If you had read through the previous post properly, you’d have seen that this wasn’t just about me — it’s been an ongoing pattern raised by multiple people.

I used an LLM to help phrase the feedback more constructively because discussions like this often become defensive instead of productive. The original post included several genuine suggestions on how the documentation and workflow could be improved, along with explanations of why the current approach creates additional confusion and support overhead.

Instead of engaging with the feedback itself, the post was removed entirely. That makes it difficult to have meaningful discussions about improvement.

I’m not posting this to start an argument. I’m pointing out that dismissing or deleting criticism simply because it’s uncomfortable prevents useful feedback from reaching the people who could actually benefit from hearing it.

few people raising concerns is attacking the project, most of the time they’re trying to help improve it.

sure ban what you don't like, i'll just make a burner account, and if you continue to hate on constructive feedback we might have to look at taking our money out of your eco system, do ask ebla and whom ever makes the sales/advance pack if they want your ego to cut into there lively hood





i'm still waiting for some hint on what is the best way to change a variable name, but hey its all about the fight not about community

[yuri]

> it’s been an ongoing pattern raised by multiple people.

An LLM made a search, found a few posts by a prompt, including my posts which I recognized from the content. And produced a summary. It's a slop content, not relevant to be posted, should not be used for validating confirmation bias.

I've told you many times. Currently we cannot focus on the developer docs. It's fine for experience devs and we are fine with it. We have many things to do. I literally been working from morning to night 7 days a week for very long. We don't need a noise about the same issues.

Regarding the previous post about release notes. It was a security matter why it was deleted. You didn't want to read my explanation, and repeated the same.

[jamie]

ok mate you do you, but next year you'll still be fielding questions that documentation should cover, in the end i am trying to make your and my life easier

the post i am wondering about is

https://forum.espocrm.com/forum/deve...e-a-field-name

[shalmaxb]

You received answers on that post (including mine). Maybe I am not that almighty, but I work with espoCRM more than 6 years already and I had the same issue with renaming. You read the posts, but I see you don`t accept. I tried a refactoring mostly because of the fieldNames. I tried 4 weeks until I accepted, that it would be more reasonable to create the entities from scratch (I would name that "learning"). You could see the forum results to your questions as well as something, that could save you a lot of useless time. I don`t know, if bullying all the time is a targeted option.

[jamie]

4 weeks to refactor? my gods!! what a waste of time wouldn't it be so very nice is there was some documentation to help you understand it with out having to go though a month of pain, potentially destroying your whole project? it seems to me that it was you that was wasting time

yeah i read your answer it helped but i needed additional clarity about how the data base was effected

if i just went blindly "learning" on a production version of espo i would be fired and sued and the company may go under

[item]

Please Yuri,

don't loose your precious time like diamond with these kind of person.

You don't need to explain your choose or anythink else.. and just take idea or experiment of certain users.

Best Regards

[jamie]

wow fan boy much? thing is it seems yuri really likes the argument as he only ever seems to come in to criticize me not address the topic

[shalmaxb]

jamie, what is wrong with you? This is 100% troll behaviour. I wonn`t react to your posts anymore. Best way for you, go program your own CRM.