adrian

Don't forget about the "Add Children" permission on the parent template.

Is this what you are looking for: https://processwire.com/talk/topic/8733-autodetect-language/ Sorry, not a multilanguage users, so I might be misunderstanding your needs.

There isn't anything else for previewing an entire page of output. Are you interested in this functionality for seeing changes to already published pages, or just in general to save going to the page on the front end? If it's the former. perhaps Ryan's upcoming Drafts module (https://processwire.com/blog/posts/processwire-2.6.13-and-a-preview-of-prodrafts/#about-prodrafts) might be useful. I haven't seen it in action yet, but from reading the post, I think it is possible to view a draft version. Would this take care of your needs?

Please note that Nico has marked this module as "Discontinued" on its Github page: https://github.com/NicoKnoll/ProcessPreview. Obviously you could fork it and make the changes to get repeaters working, but just wanted to let you know his intentions with it.

Thanks @videokid for the explanation. I have just committed an update to the module so that it won't overwrite the name if the result will be empty. Hopefully this will allow it to work in this multi-language situation. I appreciate knowing if it now works for you as expected. I honestly don't know how anyone makes it through the development phase of a large site without this module - I would end up with so many mis-matched titles/names - the editors I deal with never remember to change the name to match. Thanks, Adrian

I haven't read through to determine if there is a complete solution yet, but please read here: https://processwire.com/talk/topic/11685-page-tree-not-visible-in-backend-after-installation/

Thanks for the update. But PW doesn't handle creating a page name from that title in the first place - the name stays blank and you have to manually enter a name. If this also what you experience? Sorry, I don't ever use the Multilanguage stuff, so not completely sure how it all works. The one thing I could probably do would be to not change the name if it would end up blank, but I want to better understand what PW normally does when entering a page title like that.

There is a protect hidden pages option in PageProtector. Or you could do: if($page->isHidden()){ throw new Wire404Exception(); } but I am not sure you whether you actually need to give users access to these hidden pages or not. With PageProtector logged in users will be able to see the hidden pages, so maybe that is OK for your use case?

In case you can't find the code for logging in with email address, here are two options, both with pros and cons: https://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/?p=89599 https://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/?p=89616 (my preferred option)

Sorry, I just looked at your site and realized you are using the video_url field inside a repeater. I should have noticed that from your original post above. The module doesn't currently support repeaters - I never had a need for it and no-one else has asked yet. I'll see what I can do about adding it and will get back to you when it's working. Completely wrong - it does already support repeaters - you just need to specify the template of the repeater in the "Templates to search" config setting. The problem with the module on your site was due to fopen not working on files at external URLs. The current version should now work on your server.

Did the database get migrated correctly? Is it possible that the field doesn't actually exist - can you check for it in PHPMyAdmin or similar. There should be a table named "field_fieldname" and there should be an entry for it in the "fields" table.

If I understand correctly, just using different browsers for different logins can be helpful. Also, the user account switcher in this horst's ALIF module (https://processwire.com/talk/topic/11666-alif-admin-links-in-frontend/) can also be very useful.

Christophe, Is this on the same site that you gave me access to last week? Let me know and if you mind me taking another look - it might be the easiest way for me to decipher where things are going wrong for you.

I just added an "Upgrade Cleanup" option. Now you can easily cleanup all of the backups from the ProcessWire Upgrade module. It lets you review all the folders/files tagged for deletion and then deletes all with one click. It covers core wire folders, .htaccess and index.php backups, as well as all site module backups. I am also hoping to do some thorough testing of the entire module and get it ready for release fairly soon - is anyone out there using it regularly? Any comments/suggestions/issues? PS If you're not already using the PW Upgrade module be sure to make it one of your defaults to install on every site - it handles PW core and 3rd party site modules.

Just bumping this thread - I have updated the title and first post to now refer to PW 3.0. It would be great to start seeing the modules directory full of modules tagged as compatible with 3.0 before it is declared stable and released. Hopefully 3.x will attract a new round of developers looking to see what PW is all about - we don't want it to look like our modules aren't being updated. Even though we all know that in most cases older modules still work in newer versions of PW - this is often not the case with other CMS's.

I bet @BitPoet is spot on with his diagnosis!

Looks like I have tried to help someone with a similar situation before and they ended up using WireUpload: https://processwire.com/talk/topic/5490-hook-for-wireupload-filename-images/?p=53997 Does that help?

Ok, I just tested (got my own mapquest api key) and am getting the same error as you - this is something that will need to be dealt with before PW tries to sanitize the file - there is no file extension, so it doesn't know what it is. Either way, the error is coming before CUN gets a look in, so it won't help in this case. You could use wireUpload I guess, or maybe hook in earlier - perhaps Pagefile::filename - I'll keep digging.

Ok, I just checked with a filename over 260 characters and it uploaded ok, but didn't get renamed by CUN. Not because of the length, but because the filename didn't end in .jpg, .png etc I just used this is a test: http://domain.com/image_name.png?test=565675765675675675625625625672567256256254672567256256256725167256526725672567253625679267829647218546152412346725876651266781624582678512676567247625875267456255269759766786736738673678467836782357653675438762354675375 I can take a look at making CUN support things like this if it would help. PS - it was actually renamed, but the "test=1267686....." remained on the end.

Just something quick to try. Instead of: wire("pages")->save($pageModel); what happens with: $pageModel->save(); As for that selector - can you post what it looks like after all those variables and constants have been parsed so when can see what is actually been sent to the PW selector engine?

Hi Dave - I just tested CUN again with an API upload and it's working fine - can you please post your API code so I can take a look. EDIT: This is what I am using: $page->of(false); $page->images->add("http://domain.com/the_image.png"); $page->save("images");

It should definitely work through the API - let me take a look to confirm that I didn't break that functionality at some point, or that there isn't an issue with it and PW 3.x or anything else amiss. Will get back to you shortly.

Hi Dave, Custom Upload Names should take care of it: http://modules.processwire.com/modules/process-custom-upload-names/ EDIT: Otherwise take a look at hooking after: Pagefile::install - you can either pull the code from the hook from the above module if you'd like.

If you are going to shamelessly self-promote, you should at least provide a link to Media Manager: https://processwire.com/talk/topic/11224-media-manager/

Man - you aren't just on fire at the moment, you are ablaze Nice work - I have used Blueimp on some other projects pre-PW and loved it, so thank you!