Jump to content

hellomoto

Members
  • Posts

    388
  • Joined

Posts posted by hellomoto

  1. I have a Pages field with a PageListSelectMultiple input fieldtype, and I cannot limit it through the "custom PHP code" filter in its settings. I don't want hidden pages to be selectable, because the field is supposed to be to select pages to be included in a frontend menu. How can I do this? and it would be nice to be able to use the custom php code way to filter...

    Also, I cannot install, or activate, rather, TinyMCE. It's claimed to be compatible with 2.5... I install it, and when I try to activate it, without fail, it "activates" CKEditor, which is already activated by default, and installs its files into the /site/modules/ directory. TinyMCE is still in there, just inactivated and useless, being that there's no workaround to activating modules besides from the admin (that I know of, and it should work via the admin anyway). I also tried using BatchChildEditor (supposed to work with 2.5) -- don't seem to do anything when activated. I selected some settings and nada.

    Does anybody have any idea why I might be having these problems? I got all green for all the install compatibility checks...

  2. IF this module ends up being is a goer (security implications sorted n'all) would it be possible to have some way in the admin of letting the user copy the short url to that page. I can see where this would come in handy for a site or two.

    Is this really such a security risk..? ...that people could guess IDs? It's not about whether those pages are indexed by Google; the same risk definitely applies to the default slug-based permalinks -- like Adrian said, he'd assume they would already be publicly inaccessible from the server-side, me too; it's no more secure than not doing so and leaving the regular slugs (unless you have yours or your titles randomly generated as complex strings). Or am I missing something?

    Anyway I can't wait to try this out, thanks much.

  3. Great module but I have a little problem.

    I have a news article template named "news_item" which has title, date, text and image fields. On my news page I'm allowed to create new children with the news_item template. I've further created templates for news_year, news_month and news_day. These are empty templates with just the title field.

    I've set-up the Date Archiver for the template "news_item" to use its date field as the date, and to use each of the news_year, month and day templates as per. However, now when I create new news items they get archived correctly up to the month but for the day a new page is created every time resulting in duplicates.

    E.g. if I posted two articles today they would be archived:

    news/2014/03/24/article

    news/2014/03/24-2/another-article (although 24-2 is still displayed as just 24 in the page-tree)

    Furthermore the day page is created using the month template even though it's been set-up to use the news_day template.

    Is there something I'm doing wrong?

    I'm having the same issue, but I'm only using the year -- and using PW v2.4, which isn't specified as compatible anyway...

  4. So this morning I've come back to my PW project that I just installed on my localhost and started working on last night, to find that nothing loads aside from the homepage. Other pages or the admin area do not load anything.

    I had set aside the original template files in a subfolder called "original" and was working on a fresh theme. Seems this was the culprit. Why? What files do I need to keep of the original template files so that everything doesn't fail to load?

    Thank you...

×
×
  • Create New...