Soma

NO need to post 20 post about the same all over the forum. There's misunderstanding that this is not a fieldtype but a technique you can use in custom selector for page select, so it is dependent on the selected value of another page select on currently edited page. This is in PW since a long time and not documented. But once you set it up it's using ajax to populate the selects, so is something that requires backend page editor context. This isn't something you can use on front-end just so, or form-builder (AFAIK).

@gebeer, yeah I said that but also said that another selector would be required and that I didn't know if that would work. But I just tested and it works fine. What you need is this type of selector: "select_page=page.select_country, select_page!=" Setup "select_page" = would be page single page select field on your option pages to select its "reference", like "Zürich" has selected "Schweiz", and so on "select_country" = would be a normal page select on current editing page to select from a parent of countries. Nothing special here. Then use a page select to select cities that are dependent on what country is selected: "select_area" = would be a normal page select on current editing page to select from cities. Here you would use the custom selector option for the input like: "select_page=page.select_country, select_page!=" And so on. You can go further and create a page select that is dependent on the selected city and add a "select_event" that then uses same selector but with using "page.select_city": "select_page=page.select_city, select_page!=" This allows dependent relations using a page select instead of a parent relation. This is only for backend.

Dependent selects is not fieldtype but a technique to use the custom selector for the pagefield inputfield. You can use 'page' or 'page.field' in there to make one select dependent on an other select on the same page when editing. Ie 'parent=page.anotherpageselect'

Ah, thanks for the hint. I see now this is s leftover from a earlier version and forgot to change it there.

You should contact the module author. Nothing wrong with WireDatabasePDO. It seems a problem with ChangeLog https://github.com/teppokoivula/ProcessChangelog/blob/master/ProcessChangelogHooks.module#L417

@bacos where do you see/read this method of setting the theme? It's never mentioned somewhere and it's not the way to do it. That setTheme is protected and not part of public API. Read https://github.com/somatonic/MarkupSocialShareButtons#themes

That should work fine. But I don't know what the markup is so there could be side effects for other hidden elements?

What about 1.1.1970 then?

The module states that it's not for 2.5. Last update 2012. Thanks for reporting. Maybe file an issue on github asking for update?

It's rather: be careful of using PW dev, it can break your site. You'd never update a live site without testing it in a dev environment first.

Strange is that: - Duplicate entry '41-0' for key 'PRIMARY' - Doesn't look like "pages" db table. Its primary key is "id" and that can't be "41-0". So I'm not sure. There's also indexes for parent_id and page_id maybe it's one of those. But then 41 would be "admin" and not guest. I got lot's of these when doing multilanguage back then when it was relatively new and had some bugs that took a while to get me into. /http404/ and "guest" definately hints at a script or module that is run via a layzcron or real cron, in a template etc. Sure a search for a "->save(" in your site folder might help to narrow it down.

FieldtypeMulti hints to fields like a image, comments or pagetable field. The http404 hints at it's either the 404 page. Or a URL that is called that doesn't exist and that renders the 404 page but I'm not sure if that would result in a /http404/ (but could be). I have had errors shown and searched for hours until I realized it's a $page->render() I use in templates and the path the error logs was the url of the rendered page (partial) and not the viewed page. Or it's a export or import script (cron script) or bootstrap script. I think those also would end in a /http404/ as I had lots of these in the past. It might be a page name "41-0" in "pages" table. But since that not a PRIMARY it might be a language name field like "name1038" where 1038 would be the language id. See if you can find a page with that name maybe it's in any of the fields. Does it happen frequently, how many times, when. What modules have you installed. What fields. All might be a hint at where to look for.

To all those with special cases. Why not just create an Rss manually? Few lines of code really. If after all you have to loop them anyway I don't see why use a module for it.

Have you allowed link attributes in TinyMCE?

http404 doesn't necessarely mean it was on 404. Guest because it is triggered by a visitor. But can be amything. A cron script or a template or module.

Try $pages->find("template=visit-detail, limit=10, sort=sort");

Turn off session fingerprint in config.php.

You can make field global like the title.

@lostkobrakai There's in config.php for that problem. $config->pagefileExtendedPaths = true; Apart from that there's no limit in PW, going for millions may require special and different strategy depending on what it is built for. After millions of pages a fulltext search on large text's can grow linear quickly to several seconds. One also just have to take care about what code you build and it's easy to run into timeout or memory limit if you don't be careful. Also it depends if there's a lot going on like lots of user that post something. PW handles that all well but depends also on what server.

You would not loose anything. You can add objects to a normal array and later can access them and they're still a Pageimage with all its properties.

Why do you need WireArray? It can be a normal array and store images in there.

Can you give access? What is the code where you output and see HTML tags? Do u you have a HTML entities formatter set on that textarea? Cause that converts to entities you then see the <p> on frontend.