phpwcms Support Forum

Deutsch

Hallo,

vielleicht steh ich grade auf der Leitung und überseh da was.
Also, ich habe ein dreispaltiges Layout. Links die Navigation, in der Mitte den eigentlichen Inhalt, der je nach ausgewählten Menü angezeigt wird und rechts eine Infospalte.
Mein Problem ist jetzt die rechte Infospalte. Dort soll praktisch immer das gleiche stehen. Normalerweise baue ich dann die rechte Spalte in`s Template ein. Aber - schön wär´s, wenn auch dieser Inhalt über den wysiwyg-editor verändert werden kann. Wenn ich jetzt aber rechts einen Contentpart einfüge, dann müßte ich ihn ja für jedes Menü anlegen und wenn sich was ändert muß man es überall ändern oder kopieren. Das wäre recht unpraktikabel, da es ziemlich viele Menüs und Untermenüs sind. Gibt´s da irgendwas, was ich vielleicht übersehen habe?


English

Hi,

maybe I´m standing on the line
I have a layout with 3 columns. Left is navigation, middle is content and right are some infos. The infos on the right are always the same. When I include the content of the right column in the template, it`s not editable with the wysiwyg-editor. And when I make a content-part for the right column, I have to make for every menu a content-part. But there are many menus and when there is something to change, I have to edit or copy the content of the right column many times. Is there another solution?


Grüzli - Andi

Hi wingover,

that´s very easy. You can use the RT {SHOW_CONTENT:xxx}.
--...--/index.php?PHPSESSID=0c5e60fbd89 ... &board=8.0

Second an other alternative are the user contentparts.

Gruß Knut

Hi wingover,

as far as I'm understanding your concern, this is how I will try it for my next project:

I made two (invisible) categories: cat "premade" is holding a bunch of premade pages with premade content parts just for copying them into a new article / category, cat "aliases" is containing the needed content part aliases defined on the basis of the content of the first cat.
Now I only have to copy the necessary ones (either premade or alias) into my articles and can change them in one place (the aliased ones).
Did I get you right and does this sound practicable?

Greetings
claus

Hi,

why you don´t use the RT {SHOW_CONTENT:xxx}??
It´s is very practical. One or more WysiWyg-content for all sides.
User haven´t any problem to use this specific contentpart at there === hidden === section.

Gruß Knut

Knut,
you are right! I just ask myself how to get around filling in these IDs and the one advantage of aliased content is the front end rendering if the content part contains RTs itself, isn't it? Otherwise one has to stirr up the core files to get around this issue.
I used the show_content and it is very practical indeed.
I further ask myself how to make life easier for editors who just are going to type some text without the need to "code" RTs into their articles. So I came across the solution mentioned above - just copy and paste. Perhaps a mix of it?
So many questions left (at least for me - still struggling to get along with phpwcms)

Greetings
claus

Hallo Knut and Claus,

thank you for your answers. That was exactly what I was searching for.
In think for my current site {SHOW_CONTENT:xxx} is a good solution.

Da hätte ich ja normalerweise selber rausfinden sollen, gell.
Aber vor lauter 'eigenen reptags und php-scripten erstellen', habe ich das irgendwie übersehen.


Vielen Dank für eure Hilfe

Andi

@ claus,

Mmhh! There is no RT for userhandling.
e.g. a small example: http://www.ne-paneeldecken.de at the right site.
Template: These site is using only three Templates de/en/nl (Isn´t complete translated at this moment).
Contentpart:

--------------------------------------

--------------------------------------
At this site the user dont´t play around with the RT. He did only put his text into the two Contentparts 348 and 349.
No problem for them because the whole content for this site is generated out of the ==hidden== structur by using contentpart-alias.
Keyword: "several times usable articles".
An other stuff: ========== linking out of articles using contentpart-alias.
The upper right box are only a link section for theese. At this moment we haven´t a alternative to do this. Keyword: "Relative linking"
The box is filled up at the master structure. I have discussed with Oliver about this, but it´s a very complex issue.
The same for a copy of an complete sidestructure with half-automatic generated alias as a backend-tool.

Gruß Knut

Knut,
I'm now getting what you mean. With your example the code already is sitting right in the appropriate template - then indeed there is no need for the user to handle with RTs, just editing the needed cp - and simple, but effective! But having several templates and recurring content here and there but not the same at each place? My primary intention was/is to make the whole editing process as easy as possible for an editor (let's call it "idiotensicher")

Greetings
claus

Hi claus,

your concept is very interesting for me. I will look to your next project.

Gruß Knut