View dependency support in repeater OR PageTableInline

[Nico Knoll]

Hey,

I would like the repeater to fully support view dependency. At the moment it works sometimes. Sometimes the new values won't get saved after hitting the save button or the field will be shown the whole time.

It would be enough if the "=" comparator would be supported completely.

I know this hacky solution where you have to uncomment the following code in config.php (even if I don't know exactly how it works):

/**
 * Settings specific to InputfieldWrapper class
 *
 * Setting useDependencies to false may enable to use depencencies in some places where
 * they aren't currently supported, like files/images and repeaters. Note that setting it
 * to false only disables it server-side. The javascript dependencies work either way. 
 *
 * Uncomment and paste into /site/config.php if you want to use this
 * 
 * $config->InputfieldWrapper = array(
 *	'useDependencies' => true,
 * 	'requiredLabel' => 'Missing required value', 
 *	);
 * 
 */

But even with this set to false it sometimes stops working...

It would really important for my current content creation model:

I use "content section" repeater where you can choose the type at the top (normally "text" and "image(s)"). So the body field only needs to be visible if "text" is selected and same for the images field.

At the moment I don't know a solution to handle this smarter (maybe PageTableExtended but haven't tried it that far).

So ... yeah that's my wish

Thanks,

Nico

[apeisa]

PageTableExtended will be superior solution for this. Played with it recently, and it's very nice concept.

[mr-fan]

PageTableExtended will eat this like no repeater before....

[renobird]

Nico,

I used to have the exact same setup (it still lingers on a site that I haven't transition to PTE yet). In my case, it always seemed to work great. However, it sounds like Ryan has no plans to provide any further dependency support for repeaters.

I'll be moving the repeaters shown above to PTE soon — just feels like a better solution. 

[Nico Knoll]

It would be nice to at least have something like "PageTableInline" than - otherwise I will have to open a modal for every page section which can be really annoying if you have a lot of them

[LostKobrakai]

PageTableInline is really the thing I miss the most about "repeatable" parts of pages. Directly followed by settings to change its behavior like from multiplier to textareas profields. Either free adding of blocks, but maybe limited in number, or a fixed number of them which can be labeled, e. g. a page with three profiles (image, headline, text) and being able to call it like this:

echo $page->profile_1->text;
echo $page->profile_2->text;
echo $page->profile_3->text;

Funnily I've not used repeaters for a bit of time now, they are kinda useless for most of my usecases.

[adrian]

It would be nice to at least have something like "PageTableInline" than - otherwise I will have to open a modal for every page section which can be really annoying if you have a lot of them

I completely agree, except it should be PageTableExtendedInline - to me that would be a great interface - need to think about how complicated this might be to put together

I also don't like the modal approach of PageTable - that is definitely where repeaters have the edge - that said, repeaters have too many limitations so I don't ever use them.

[apeisa]

I think it would be reasonable simple to add inline editing into PTE blocks case by case, but saving would be simpler as ajaxified, not on regular page save.

All inline editing is damn hard to do in general manner when you have markup agnostic system like pw. I have tried on front end when building Fredi, and yes, easy with simple text, difficult with anything else.