horst

Hi @MarcoPLY, welcome to the forums. Imagefields are tied to a page, therefor the images you upload through this page are stored under /site/assets/files/<ID-OF-THE-PAGE>/. You are using repeaters, maybe as one of multiple options to reuse fields on a single page. Repeaters are also pages (behind the scene), therefor the images you upload to a repeater item are stored under /site/assets/files/<ID-OF-THE-REPEATER-PAGE>/. For all images you want to use in multiple places, one recommended way is to create a hidden page with an imagefield. Some people don't create an extra page but uses their homepage for that. Both do store all the stuff that is needed on multiple places, also text like contact data, files and not only images. But let us focus on the images now: If you need them into different pages with ckeditor fields, you need to click on the images button. In the opened dialog you can read " If you would like to select images from another page, select the page below.". Below is the name of the current page and a button or link called "change". Clicking on it opens a page tree to let you choose another page. (The homepage is the first one, what may be the reason some people store their reusable stuff there). With clicking on the pagenames you can traverse through the tree to every single page that exists in your system. Clicking "select" on the page of your desire displays all its images as thumbnails.

Since today, 31-01-2018, we have support for this in the PW Core. Therefore I updated this module to version 2.0.2 This version handles the detection of the core support and dismiss its installation then. If the core module is available but not installed, it get installed instead of this third party module. If you have this third party module already installed since a previous PW version and upgrade your wire folder, this module will detect the core module and install it. Its own hook isn't registered then and you get a notification about the changes.

@flydev What about the UAC (User Account Control) in windows? Is it enabled or disabled?

I would doublecheck accessrights on C: under windows. If you have a drive with another letter in front, try to use this. Also, it isn't necessary to use backslashes on windows as long as you are inside PHPs functions. (Backslashes are only necessary on the windows commandline, via exec() or system()). Also I would try a directory downsite the DOCUMENT_ROOT, maybe under /site/assets/files/0. Just to compare if it does work there or not. Maybe not much of help, but I'm a bit out of ideas. EDIT: Apache / PHP security setings like opendir / openbasedir restrictions or something?

@hezmann Original text from the config page: But you don't need to start with ListerPro. You also can configure the core Lister to get a good impression on how it works out.

My first PW-project was a site profile for mp3 database. There are genre, autor, album, track siblings in the tree. To show them as parent children relations, I used a jquery tree in frontend. So, it was my first contact with PW, and I doesn't know much about it. But maybe build your own tree as a process module, which has its own page(s) under admin, can be a good solution, too. http://modules.processwire.com/modules/local-audio-files/ There is a basic demo page too: http://pwlaf.biriba.de/sitemap/

I'm not aware of any module that modifys the page tree beyond hiding some pages, and never would even think of to try. I go with lister pro and its filters for stuff like this, because it is damn fast and easy to use.

If I get you right, you want to show one page on multiple places in the page tree? I don't think this can be (easily) done. What is the reason for this? Maybe you can solve it using the lister view?

I'm not sure if it is worth the (for me ATM, not available) time to add new functionality to this module as we got the "focus point thingy" now in the core. When this get a zoom functionality too, it is much much easier to use for authors and devs too. https://processwire.com/blog/posts/pw-3.0.89/ @adamspruijt

Cropping now can be done via a focus point, directly in the core image fields: https://processwire.com/blog/posts/pw-3.0.89/

To get a "quote" how useful it maybe for a specific site, log all (search bots) user agents for a while.

Look here, there is complete upgrade procedure with help:

ähhm, ok. Now I've learned something new. I wasn't aware that a single csv file already is a "pw language pack". Until today I thought it must be a bunch of little files.

Yes, that's the prefered way for those use cases.

Hi and welcome to the forums, @duncan That's a very well first post! Do you have this also in form of a pw language package? Or is it easy to generate one from your source? ( I personally haven't done much in regards of translation files, only downloaded and installed ready to use language packs from here: http://modules.processwire.com/categories/language-pack/ )

There is an option in field settings input tab:

Hi @Chris, you PM'ed me with the question if I once had written a module that creates one page per uploaded image. No, I never had. But those questions are better asked directly to our friendly and helpful community. I remember too that there was something, but was it somas images manager? or does anyone else has written something among that line? If there isn't anything else around here, you may strip out the upload and page creation process from somas module.

Thanks for the tipp. I think it will be easy to find a solution that can work with the feeds.

Maybe a dump question, but how or where can I configure Github to get email notices of every commit to the PW repository? I get a lot of emails for issues, but currently not for commits. Any hint is much apreciated.

Oh, thats perfect and simple! Just change a $config var before rendering starts!

Yeah, what the long subject says. I need to know which JS part (code) or which event handler is responsible in a ProcessPageEdit page, because I want to disable it for a specific page in a specific state.

I have a question related to security. AFAIK in a lot of shared hosts that are based upon php as apache module, not a cgi version, the php www-user only (should) have write access to files under assets, not modules and templates. Is there a way, workaround, for those cases to use the module too?

But maybe this CKE-plugin is an addition for AOS? @tpr If tpr adds it, @marcus you may only check if AOS is installed (incl. the min version this plugin gets added) and displays a reminder.

After some testing I now use a simple HTML file field embedded into a InputfieldMarkup: public function hookAfter_ProcessPageEdit_buildFormContent(HookEvent $event) { $p = $event->object->getPage(); if('my-desired-template-name' != $p->template->name) return; // early return !! $form = $event->return; $uploadField = "<input type='hidden' name='MAX_FILE_SIZE' value='{$this->MAX_FILE_SIZE}' />Diese Datei hochladen: <input name='userfile' type='file' />"; $f = $this->modules->get('InputfieldMarkup'); $f->attr('name', 'my_markup_fieldname'); $f->value = $uploadField; $form->add($f); // write back the modified form $event->return = $form; } In init or ready I check for the file fields value, and if a file is sent, I validate the file and add it to a hidden PW file field of the page.

Hi @kongondo Is it possible to use this in pws backend page edit? Maybe in junction with a hidden files field?