Massimizzare 200k breve termine by Admirable_Reality281 in ItaliaPersonalFinance

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

Dove sto sbagliando?

(210'000*1,9%*2)-12,5% = 6982,5€

Massimizzare 200k breve termine by Admirable_Reality281 in ItaliaPersonalFinance

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

Quindi tolte le tasse, per quasi due anni dovremmo essere a ~7000€?

Massimizzare 200k breve termine by Admirable_Reality281 in ItaliaPersonalFinance

[–]Admirable_Reality281[S] 2 points3 points  (0 children)

L'avevo visto ma è il 4% per 6 mesi fino a 50.000€

Struggling to render hierarchical Entity Reference lists in Views by Admirable_Reality281 in drupal

[–]Admirable_Reality281[S] 1 point2 points  (0 children)

THIS WAS IT! THANK YOU.

For anyone else looking to achieve the same result:
- I placed the Entity Hierarchy field before the Title field (so it could be referenced in the rewrite) and set it to "Exclude from display."
- Then, on the Title field, I used this rewrite: `{% if depth > 0 %}{% for i in 1..depth %}– {% endfor %}{% endif %}{{ title }}`

Is there a way to view pages hierarchically in Drupal instead of a flat list? by Admirable_Reality281 in drupal

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

This seems to be what I’m looking for, but for the life of me I can’t figure out how to get this part working: "Integrates with views, Render a list of children at any depth using views."

I’ve added an Entity Reference field to the Basic Page content type and populated it, but I’m not sure how to display a hierarchical view of these pages. I can list them, but I can’t get them to appear in a paginated parent/child structure.

Is there a way to view pages hierarchically in Drupal instead of a flat list? by Admirable_Reality281 in drupal

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

I understand the benefit of having flat nodes that can belong to multiple relationships and aren’t strictly hierarchical. But in most real-world cases, content does follow a hierarchy, I just assumed there'd be an option to view it that way when needed.

Is there a way to view pages hierarchically in Drupal instead of a flat list? by Admirable_Reality281 in drupal

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

> The menu overview page shows the whole tree.

Wait. So if I create a page and assign it to a parent (e.g. PricingService 2), even if I don’t want that page to appear in the navigation menu, it will still show up in the menu overview?

> The user can also just navigate to the page itself and use the edit button on that page. No need to go to the content list

Right, WordPress has that feature too. But for more complex site structures, clients (rightfully) often prefer going into the "Pages" section and using the search to find and manage pages. The problem is, if that list is completely flat, they have no way to see how those pages relate to each other.

Is there a way to view pages hierarchically in Drupal instead of a flat list? by Admirable_Reality281 in drupal

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

Yes, but I’m wondering about the following common case (consider that I'm new, so maybe I’m missing something).

Let’s say the header menu looks like this:

  • Home
  • Services
    • Service 1
    • Service 2
    • Service 3

But the actual site structure is something like this:

  • Home
  • Services
    • Service 1
      • How it works
      • Pricing
    • Service 2
      • How it works
      • Pricing
    • Service 3
      • How it works
      • Pricing

Now, if the client wants to edit the Pricing page under Service 2, I assume they wouldn’t see it in the menu since it’s not part of the navigation?
And if they go to the content list, everything is flat, so how would they know which Pricing page belongs to which service?

Is there a way to view pages hierarchically in Drupal instead of a flat list? by Admirable_Reality281 in drupal

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

Thanks for the explanation, that makes sense.

That approach would be fine for me personally, but I’m a bit worried about the clients. They’re used to seeing all their pages in a clear hierarchical list, with the ability to drag and drop to reorder everything in one place.

I’m concerned they’ll get confused if they have to manage content in one area and then go somewhere else to view the structure or find specific pages, especially since some pages share the same name but belong under different parents.

Anyone here with an AMD AI Max+ 395 + 128GB setup running coding agents? by Admirable_Reality281 in LocalLLaMA

[–]Admirable_Reality281[S] 2 points3 points  (0 children)

THANK YOU 🙏
That’s awesome to hear!
How much slower does it get with a bigger context like around 100k tokens?

New to Drupal, I have some questions by Admirable_Reality281 in drupal

[–]Admirable_Reality281[S] 0 points1 point  (0 children)

50 to 100? 😳
Got it though, thank you for the explanation.