hellomoto

I'm playing around with permissions for THE FIRST TIME and I'm quite excited about the whole thing because when I log in as this other role I made I realize how much cleaner it looks of course to somebody who isn't developing the site. Anyway I have a template listing that is the default/only created under template listings. (A listing may not have children.) So then I made a role, listing_manager, you know... to manage the listings... granted permission to view, edit, and create them. Problem is, when logged in as the listing manager, I can edit the listings, but there's no "New" link to create any? I guess that's because that link is part of the listings page/template's row/branch, so... it doesn't show for its children though... which are all of the same template where the role does have permission to create. This seems like a silly bug. Any suggestions as to what might be the simplest, cleanest fix for this? or maybe I have something set up wrong? Thanks.

Thanks. I'm still mulling around on different parts of this anyway, but will definitely give the Dashboard a try, sounds like a good place to start.

Damn thanks, I'm trying to do this right now, but wrap this up in a function. Does anyone know how that might be done? I tried this: function getValueLabel($fieldname) { foreach(explode("\n",$page->fields->{$fieldname}->select_options) as $option) { $valueLabel = explode(':=',$option); $value[$valueLabel[0]] = trim($valueLabel[1]); } return $value[$page->{$fieldname}]; } echo getValueLabel("currency"); but... yeah that doesn't work...

That's what I did, but I prefer to have more like groups of settings in one page, not a page for each option of every setting... know what I mean? Like new/used, own/rent, 1/2/3. Could always change in the future but for now I want to keep it simple as possible, really just trying to get a widespread proof of concept... Thanks though. So I just adjusted that Select Drop Down module to be a radio select instead. This is fine for simple options such as those I described above, no? from a performance standpoint? Say for a few thousand listings heavy with fields, a good amount of them searchable, including these ones I want to make non-pages.

I'm looking for a way around that though, for fields such as Condition where there are only 2 options: Used and New, or Mobility Type, for which the two options are Power and Sail. Those seem like slight overkill to include in the page tree. This https://github.com/Hani79/Processwire_FieldType_Select_Drop_Down may work... What do you guys do when you have such simple sets of options? Pages, unanimously? Thanks.

I've seen that, but I haven't tried it. Probably should.

I need to make these fields for a particular template: Condition={New,Used} and Style={one,two,three}. Is there really no simple way of doing this without making Condition and Style pages with their respective children/options?

How do you guys go about designing custom admin areas for your websites/applications, for when the default page tree just isn't practical? Do you customize the actual admin area provided for client users that hides all the things they aren't concerned with, or do you just create a new admin area altogether, as you would any other frontend template, but with protected access? so as to not hack up the admin too much and leave it intact? What do you all prefer to do for your custom admin UI? I feel like the latter would be much quicker and easy with the API. Thoughts?

Thanks! Those things aren't that important for me right now, I was mostly just concerned that maybe my installation in general was buggy... Glad to have the cause for the problems identified. I did see that note in the Custom PHP Code part but for some reason didn't think it applied to the -Multiple version... bah...

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...

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.

I had that too... Actually commenting it out worked. Whoops.

I had ('localhost','www.domain.net') and it still said localhost in the view links and admin pages <title>, then I switched their order and now the links are going to www.domain.net/~username... How do I get rid of the ~username part?

How about adding in virtual URL segments like /year/month/ appending the parent page name and prepending the name of the active page? without having to actually separate them? Anybody know of a way to do this?

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...

I followed the module implementation instructions and I'm not getting a map, just a blank canvas... and an Uncaught TypeError: Cannot read property 'lat' of null. Any ideas..?

Yeah whoops I spoke way too soon, realized that a while ago. Haven't worked in PW for some time now... Glad to be though Thanks for the help anyways.

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...

Anybody know of a PW module similar to the Hacklog Remote Attachments plugin for WP?