Soma

The LanguageSupportPageNames doesn't have url segments at the end but at the start. I don't plan to support any other unusual url segment construction with this module.

This module already work with LanguageSupportPageNames module and is multi language aware, it's no any different than if you would create your own with $page->url. With PW multi language support you don't need anything different than without.

Any decent web developer knowing php will be able to step into advanced PW building without problems. Not true to other system I know of.

and that would be, I mean the eastern egg?

You can also use "subfields" like template.name, template.id ... maybe not a good example but you get the idea, most or all that can be also used in selectors like created_users_id etc.

Thanks alevine, but there's no syntax error or problem, the problem seems just creating a new class extending Inputfield. For example: <?php class InputfieldLinkList extends Inputfield { public static function getModuleInfo() { return array( 'title' => __('Link List', __FILE__), 'version' => 1, 'summary' => __('Provides an administrative interface for working with link lists', __FILE__), 'requires' => 'FieldtypeLinkList' ); } public function render() { return "<div id='linklist_{$this->id}'>test</div>"; } } So it somehow happens in Inputfield class, but there's dozens of Inputfield modules that are there working.... yeah it's mad.

I'm on a MacOSX 10.6.8. XAMPP 1.7.3. PHP 5.3.1. I changed PW version, no luck tried another install, no luck tried a plain php class not extending Inputfield, no error There's no syntax faults for sure Doesn't happen when adding new class extending Fieldtype or Process

Thanks but that's a common routine check, already tried "everything" possible (usual tasks).

I'm creating a new Fieldtype, or trying to and run into a problem that doesn't seem PW related, but it's really strange. I only happens when I add a new Inputfield module (not happens with other types!) if the error wouldn't be strangely enough already added Inputfield module seem to work. I found some infos out there but all seem not to be related and it seems like a apache/php/hardware problem. I'm lost from apache error_log: [Fri Jul 26 14:51:29 2013] [notice] child pid 584 exit signal Bus error (10) [Fri Jul 26 14:51:30 2013] [notice] child pid 525 exit signal Bus error (10) [Fri Jul 26 14:51:30 2013] [notice] child pid 524 exit signal Bus error (10) [Fri Jul 26 14:52:31 2013] [notice] child pid 586 exit signal Bus error (10) [Fri Jul 26 14:55:19 2013] [notice] child pid 630 exit signal Bus error (10) [Fri Jul 26 14:55:52 2013] [notice] child pid 523 exit signal Bus error (10) [Fri Jul 26 14:57:36 2013] [notice] child pid 589 exit signal Bus error (10) [Fri Jul 26 15:02:19 2013] [notice] child pid 3120 exit signal Bus error (10) I first thought it's a syntax error or something but after hour of trying it's all right and when I try to create a test Inputfield it happens again.

40k! We are massages pros!

The second one error, is one we already reported multiple times, but I don't know what Ryan says about it or can't remember as I haven't looked into it since then. Basicly the 404 page doesn't have a localUrl when it's thrown and not directly accessed. Not sure it has been fixed already or if it's possible.

Heh, now we got 3 mailchimp modules separately that do work differently. I'm holding mine back as it is a lot more complicated to create a good mailchimp module with remote managing lists and campaigns. Lists can't be created via API, reason being that you should work with segments and groups for a list instead of creating a list for every group. This is to avoid creating too many lists. But this get's a little more expensive in "recreating" the functionality Mailchimp already has done very very well. One thing that is different from your module for example is I don't use PW user but pages. I create campaigns for lists and submit them from a newsletter created from a special page the user can edit and select for submission. So far I haven't got the time to invest and list management is still missing, kinda what you got here but as said not for PW users. But it has a nice admin interface to create campaings and see part of statistics after sending. Thing is that to make it really efficient (as the requests are limited) it would need to have caching built in so it doesn't need to request all those informations everytime, kinda what they suggest in their API docs. We maybe should work all together I'm on holiday currently in Turkey this week, but maybe I can find some time to share module.

Ah thanks for mention. It this strange thing with versions when being 008 it threats it as octal number, although when on version 0.0.7, it shows that an update 0.0.8 is available (shows it correct) but after updating it displays 0.0.0. :/ Ryan? Edit: I corrected this with 008 changed to 8.

It's hard to tell, as your javascript doesn't make much sense with the php/html you posted. There's no link and no href. Also I don't understand what a index.php has to do with all this, guess it's a plain php you created without PW? And I don't know what scripts you're talking about you have in site/script. Really hard to help without asking a lot of questions, that's maybe why nobody yet responded.

You actually can do matrix sorting quite easy with floated elements and jQuery sortable, but the config needs to be changed to vertical and horizontal, not only vertical. I've done it for the Imagefield and it works ok.

Would you mind creating a github account and put that there?

I will soon have to create a link list fieldtype, where you could add links with url and text, internal and external. I'm surprised nobody done that yet, as it seems a basic feature a CMS should have. I've used repeaters until now and it's ok I guess too, but maybe a dedicated fieldtype would be nice. Another option is to use a Wysiwyg field as that would already allow for "easy" creating a list of links. Those are all very easy to setup option and flexible. But you know it's fun to develop for PW. Or anyone want to have a go or know if this would make sense at all?

ModulesManager doesnt care about dates.. only module version.

Page publish permission is used to control if a user can publish a page or not while still being able to edit. Nohinh to do with if the page is published or not.

Why not use a simple language file with php vars or a page with language text fields? The translation in PW isn't really suited for such forrmatted text in front end. Theres too many restrictions and the default text is like a key means once you change a typo or word you have to reenter all translations again.

I'm not sure I get what you're saying...

Not sure what you mean by can it be used... it can be used for whatever you make out of it.

There's a 'page-publish' permission you can add and use that. It's not there by default but it's recognized by PW

Using the approaches explained there are not recognized by PW itself, you'd have to take care of it somehow. There's everything explained on that page with examples. I'm not sure many people have used this method yet and I think it's not the ideal solution for real multilang sites also because of the various things you have to take care. Consider all the cases and dealing with them like links in textareas etc. And you wont get speaking translated urls. I only ever used separate tree and the LanguagePageNames, previously LanguageLocalizedUrl. It's a lot easier to deal with and setup plus the system works with it and takes care of urls etc. Consider that those docs were written before there was corr language support as with LanguagePageNames shown in this thread.

I just tested the page-publish permission, and I got same the still odd behavior as described in this thread. With latest dev version of PW. I added a "page-publish" permission to a role "publisher", the editor that has this role added can't edit pages anymore, only for unpublished pages. Once you go to the a page with access roles of editor and publisher set, and look at the settings for "Who can access this page?" when you publish and unpublish the page you'll see strange things happening to the roles and their permissions. Has this fix ever been comited or was it once in and left out on dev branch? Edit: Ok tested this little further. It seems I'm not able to stack the roles for publish permission. Like having a editor role without publish permission, and a publisher role that has only "page-publish" and "page-view" permission. editor1 guest, editor, publisher editor2 guest, editor with this setup I can't get it to work and get strange things happen. It works when I separate the two roles with publish permission and give publisher also same rights plus "page-publish" like editor1 guest, publisher (edit and publish) editor2 guest, editor (only edit not publish) Isn't it mean to combine roles like adding roles with certain permissions? Another thing when testing this, was that when I give a role edit, delete etc permissions - and then on the template I check all permissions for that role (as the checkboxes are enabled). So far so good. But when I remove the edit, delete permissions from that role after that, the setting are still somehow existent on the template access and role settings, but the checkboxes are disabled. Still yet it shows these permission for that role when inspecting a page under "Who can access this page?". Not sure what's about that, but pretty confusing. When I turn back on the permission for that role, the checkboxes are again enabled AND all checked. Shouldn't when removing permissions from a role also those settings getting removed? Those setting somehow remain hidden but still active? It's maybe a detail but maybe would explain why I seen strange things happening. Even though it's maybe not important, but I found it confusing when testing with roles and permission.