lpa

+for spaces in passwords! And no artificial requirements as uppercase and number etc. The restrictions in passwords should be freely definable in PW.

Is the latest translation in https://github.com/apeisa/Finnish-ProcessWire? Has anyone made translations for 2.5? Is there any plan for keeping this up to date with the latest PW version changes?

+1

Doesn't anybody use eclipse for PW development? I don't find a way to get the content assist in Eclipse to complete the variables like $page or $user.

Is it really so, that nobody finds this to be a problem in any case?

I can see that the support for magic methods is now in PW source code. But my question is why do I only get $config to give the hints in Eclipse? The other variables like $page, $template, $user don't show the magic method given documentation. Can someone confirm that this works with PW and Eclipse? How to make it happen?

Martijn, I know that. Even Mac, though being a unix, is not case sensitive by default. But that is not the issue. If the name is the same regardless of the case of letters, it should replace the file. I prefer the system not to touch my filenames by some algorithm, but give me the possibility to keep the uppercase letters. By the way, I like the new addition of file replacing the file with the same name that was just introduced in the latest dev-versions, because I think it was annoying that I first had to remove the file before replacing with a new version of the same file.

I have always wondered why it is not possible to keep the name of the file uploaded to PW intact? I mean to keep at least the uppercase characters in the name and maybe some special chars too. I know [a-z,0-9,_] is clean, but today most of the systems, browsers etc can handle even spaces in the filenames. There are situations where I would like to keep the names like they are in some other systems (with uppercase chars) or the same as they have been in the web before converting to PW? So would it be possible to have an option for file-fieldtype to keep the names uncleaned when uploaded?

I can't get the MP3-player to work when trying to listen samples: Initializing MP3-Player... Edit: It doesn't work on Mac 10.6.8 Safari 5.1.10. Maybe it is time to upgrade….

Antti, would you have time to update this module with your latest changes?

But when the module is ready, it should protect the files without any template level protection turned on. That's how I would expect it to work.

Is this module supposed to support securing the attached files with pagefileSecure-option in config.php?

I get an error with this info in error-log: {"errors":[{"message":"Bad Authentication data","code":215}]} I have checked the authentication data many times, but don't know how to further debug this. Could someone help? EDIT: Is this module supposed to work when my site is not yet on public IP? Can Twitter authentication work when PW is on localhost in home network?

I have a template called concert, which has a repeater called event, which has a field called concerthouse, which is a page reference to a page with a template that has fields: title, address and city. If I want to search for the concerts that are held in a concerthouse whose title I would like to search, how would I make the find on my search.php template? Simplified find with only the concerthouse.title -field: I have tried $pages->find("template=concert|repeater_event,event.concerthouse.title~=$q"), but this doesn't work. And I don't want to get the repeaters as the result pages, but the concerts. And not the concerthouse-pages but the concerts.

Finally I found a solution which kind of works: .reveal-modal { display:block !important; }

Yes, I am using the Zurb Foundation 5 profile which has 1.10.x version of jQuery. Maybe the module could be fixed to use .on?

I get this error on my browser: [Error] TypeError: 'undefined' is not a function (evaluating '$("li.PageListActiondelete a").live("click", function(el){ if(!confirm("Are you sure?")) { return false; } })') (unknown function) (ProcessPageDelete.js, line 2)

Shouldn't it be possible to search with rootParent=/somesection/ with batcher?

I would also like to see that the requirements of the password complexity could be defined without hacking the core.

I have still this problem. As I wrote, I use Foundation Reveal Modal with Ajax loading: <a href='{$k->concertplace->url}' data-reveal-id='kpModal' data-reveal-ajax='true'>PLACE</a> <div id='kpModal' class='reveal-modal large' data-reveal > <a class='close-reveal-modal'>×</a> </div> In concertplace.php I have: $map->render($page, 'map') And in main.js I have: $(document).on('opened', '[data-reveal]', function () { setTimeout(function() { google.maps.event.trigger(mgmap1, 'resize'); mgmap1.map.setCenter(mgmap1.options.center); }, 350); }); The map still doesn't load properly. The other content of the Reveal Modal is ok. What should I test next?

Adrian, No that is not perfect for us. We need the urls to be easy to remember. Lets have an example: We have an event called "April Event 2014" and the registration would be at http://www.eventregistration.com/register.aspx?id=2344,enter=567. I would make a redirect http://www.ourdomain.com/aprilevent2014/ -> http://www.eventregistration.com/register.aspx?id=2344,enter=567. Now I can print this http://www.ourdomain.com/aprilevent2014/ in all the ads we make for the event on print etc. And if we have many redirects for different purposes, an info field would be helpful to put info about: how long do we need this redirect, who is responsible for this etc.

We use redirects for exampel for temporary addresses that redirect to temporary questionaries or registration forms for events etc. Those addresses will be used in print and have to be easy to remember even when the actual registration happens in a complex address with many attributes in the url.

I would store just the reason this redirection is done, when and how long do we need it etc. Instead of keeping that kind of information in an excel-file that no one finds...

Hi Antti, I would love to see one more field for this module: info-field for storing the reason for this redirect. Just a small textarea where you can write something. Could it be possible to have this?

Thanks Ryan for this help. I think it would help if the API documentation would describe when I can use filter('/path/to/parent/') and when not. :-D I feel sometimes that the documentation should be more detailed and contain more examples. But the new cheatsheet seems very promising.