MadeMyDay

The name is a bit misleading. Just look in the modules section in your backend under "install". It's distributed with every core version, not installed though.

Look here

As said on GitHub: Compatibility should be given up to newest PW3. Look in the dev tools, if there is a JS issue. Never encountered something like this. "textblock" has a template associated? Without template there will no render in PTE. But shouldn't prevent modal though. Please show Console Output.

Well, just saw this: https://github.com/somatonic/Multisite/tree/dev2#troubleshooting My screenshot refers to an older version of multisite (2-3 years maybe?!), but it works... so better wait for Soma. ;-)

Hey Reno, first, you don't need to have the main domain as a child of the root document. Second, it should be possible to have the subdomain folder somewhere in the tree. Afair the module matches the page name and then rewrites from there, so it shouldn't matter where it is nested in the tree. But Soma surely knows better ;-) From one of my sites:

By far many more than multisite module for PW (haven't encountered many bugs in all the years). And also more expensive

You don't have to refer to the page tree order or use $page->children. Assuming your PTE field is called "layout" all you have to do is: foreach($page->layout as $l){ $layout .= $l->render(); } The field itself holds the connection to its blocks. No matter where they are in the tree (because that's configurable).

@all: Was kind of out of business for a while. Will come back and check everything in September! Also some new ideas for this module ;-)

Look for pageTableExtended.

Come to the booth IN the conf breaks and find out ;-))

I am also there as always. This time running a sponsor's booth. Try to find and recognize me ;-) (Yeah, I know, webrocker... Should be easier at the warm up, just head for where the wheat beer is)

Hehe, yeah. Glad I could get that through

haha, fair point. Typical last minute change, navigation was centered before ;-) Thanks, man. Soma: That ugly?

And another one: http://unternehmensberatung-nrw.com/ Small german business consultancy, no english version needed. Target audience is only german. Pretty basic stuff PW-wise. Everything editable, icons, all texts, even the charts.

Another one out of the door: http://apollon.de Pretty basic usage of PW, pagetableextended for the content blocks, flexible sidebar, some effects (their wish)

Why not? The only thing you have to do is to identify PageTable parts, put the page containing the PageTable field in an array and display the results only once. Or what do you mean? Edit: Ah, you mean, you have to search in more fields than just one? Well, also this is not a show stopper

Why not use PageTable or PageTableExtended for that? To the topic: I also don't see a use case where I allow my clients to insert editable images directly into a RTE field because I always want to separate design and content. But nevertheless if I needed it, this implementation is just awesome. And the upcoming ability to generate thumbs of a given image in the standard image field – even as a byproduct – is the thing I am looking forward to! What I don't quite get: All the features described above (see quote and posts before that) are already achievable with PageTable and PageTableExtended. The module still is in early stage (had no time to develop it further) but works pretty well and allows to define custom layout parts. A next step would be to get rid of the popup while editing and put the edit interface into the layout itself (shouldn't be hard with an Iframe). But I would never advocate a WYSIWG editing capability because editors then tend to "make the content fit". And this can never work considering the unexpected output on other screen resolutions/devices which an editor can't foresee. So my approach is to make the interface as clear as possible and present the content in a comprehensible way, but never in a 1:1 way, because this can never be real, neither in front- or backend. Edit: Take this page: http://schutzbelueftung.de/montage-service/ This it how it looks like in the admin (cut-out):

What exactly don't you get?

Thx vxda, fixed. Since you also can swipe the images, I don't see the necessity in enlarging the arrows on mobile though

Okay, should be better now. Thx you both!

Okay, that's odd. While I can see a potential problem when there are more than 4 images on the left, your screen tells me there is something other going wrong. Have you just resized the browser window before opening the machine? But I will try in Windows anyway, thx for the screenshot!

Thx for your feedback. Which resolution? Should be visible usually.

New year, new site online http://schutzbelueftung.de/ This time industry client, they build ventilation systems for diggers, earth movers and stuff like that. Pretty interesting. English version is in the works, should be ready by march. This is the second page featering my pagetable extended module, with which the client can easily build an individual layout out of predefined layout elements. That means: Everything on the site is filled by the client, all images and text. One special thing is the database of their installations: http://schutzbelueftung.de/aufbaubeispiele/ Here you can filter by company, type field of application. This is done by ajax in the background, so easy to build with the PW selectors <3

I use soma's module on different sites without problems. Some with root set as one domain, children pages with others and some with different children pages and root not defined as domain. This cannot be the problem.

You could use PageTable for that. So at least your overview is narrower. Customize the columns and you're done.