planmacher

I found a solution - even though I don't understand in depth, what is going on:

The Userrole not only needs the right to delete the content-element  pages, but also needs the right to use the delete button in the pagelist:

=>modules => processPageList => allow trash for non superusers

Perhaps this will be helpfull for others ...

Now I got a problem deleting content-elements with non admin user role.

I have a user role which have the rights to edit, add, create, and delete content-elements (see attachment). But with this role - after asking, if I really want to delete the element - nothing happens. The element is still there...?? 

With admin role it works!

Hello,

I am new to this module and it works great - many thanks for it! 

Is there a way to style the elements in the backend in another way than the frontend? I found the content.css in the modules directory. There I can apply changes for the backend elements - but will they be lost after an update of the module?

Thanks for that!
I will think it over and see, what works best for me!

I try to geht frontend editing to work, but there are js errors.
There are hints in the forum concerning jquery versions. I use some jquery for the frontend - at the moment version 3.6. 
When I delete the jquery reference in the head of the template, then frontend-editing works fine. In the other case it works too but the field editor ist shown very narrow to the left side of the modal.

So what ist correct way to handle both, jquery for the website and for frontend editing?

Update:

Could fix it by myself with moving all my script references from head to end of template file.

Thanks for your reply and the module!  I will give it a try...

Hello, is this module still necassary with newest PW ?

What ist actually the best way to show a text input field only if an image field ist populated? This image field is set to "single file if populated, null if not".  Additional the text input should be "required" if the image field is populated. 

Any help is appreciated...

Hi,

first I thought everything works well, but then I recognised, that there ist a problem with image description fields.
No matter what I write in the description - there ist always some error like: 
Unknown Selector operator: '[empty]' -- was your selector value properly escaped? field='Unser', value='Igel aus dem Bi', selector: 'Unser Igel aus dem Biotop, sort=sort, parent_id=1016, templates_id=43'

I even made a test environment and updated the pw version to 3.0.200. Then I tried the core export feature but it throws the same error!

Am I doing something wrong?
Anay way to skip the description field?
 

Shame on me - and in good old german: Wer lesen kann ist im Vorteil ?

So this can be closed! Thanks!

Thanks - I found this out a few seconds before your post ?
But I don't understand it. Because the image ist only about 500kb. Perhaps you can explain this behavior?

Hi!

I just installed a new and clean pw 3.0.200 and use the client side image resize for an image field.
Minimal width has to be 1800px - minimal height 800px.

Now  - when I upload this image with 1920 x 1282 Pixels ...

processwire tells me, that the image is too small in dimensions.

So the image seems to be resized without any reason.

Any ideas??? Thanks!

Hi,

I have to export some pages from a 2.8 installation to processwire 3. 
Is this module a possible way to do this?  

Thanks for any help!

Hello - Thanks for your great module!

I have a special need for the side, I'm working on right now:  Is there a possibility not to show the "result_summary_field" in the rendered results, but the 'near' content of the search-match in the search field itself - with the match highlited?

So lets say there is this content in the search_index field: ' Hey - this is just a simple little test for the search engine!'
I am searching for the phrase 'little'.
The rendered result now should show me lets say: '... just a simple little  test for the s...'

To be honest: My php-skills are not that good to understand all the files of your module -  but as far as I can see, I am afraid that it will not be possible in an easy way to change the code for my needs!? 

Thanks for any reply! 

Hey!
I just installed this module on a fresh PW  3.0.123
Everything works fine - thanks for that!
Little Issue  when the size of the description field is set to "0": After upload of an image, the input fields of the extrafields also are missing - only the labels are visible.

After first save everything works correct!

Hope, this was not discussed before ... - thanks for any help!

Hello,

this warning still is shown on the modules page in the backend. Or am I doing something wrong?

I have just upgraded from 2.7 to 2.8. 

Thanks for any reply!

Yes, that's ist.

Thanks alot!

Hello, I am using PW 3.0.62 and have trouble with inputfield type file.

After uploading a file the icons for deleting and moving-up are lying over each other - so deleting is not possible.

Found this problem in two different installations - so I think its a bug?!
Any help? Thanks!

On 10.8.2017 at 11:35 PM, Robin S said:

But it may not be such a good idea to open a new repeater item on page load. The issue is that you are actually creating a new repeater item when you do this, so that if the user saves without filling out the repeater fields you will end up with a blank item. And if any of the fields in the repeater are required the user will see error messages.

Thanks alot and please excuse my late response!!
You are right - not a good Idea - I realised it by myself, that there is an new repeater Item created by opening the input mask. Nevertheless its good to know, how to do it - will give it a try - and its great to see, that there is such a great community with a lot of help here.
 

Hi! Hope somebody can help me ...

I don't want the user to have to click on the "add new repeater item link" but would like to open it automaticly when loading the edit page. (Best would be, if this only happens if the new item would be the first item) 

Tried to do it with triggering the click of the add-new-item-link with javascript. But this does'nt seem to work. My java script knowledge is really poor :-(

Or do I just missed something in the settings of the repeater-field???

Thanks for any feedback!

Hello,

very stupid - sorry!
I played arround with permissions on system templates - now I cannot login anymore. Always get redirected to 404 Page.

Even more stupid: Can't really remember what I did last.

Tried to give a special role access to the roles Page. My thought was, that I would have to give this role access to the system templates (roles/admin/...) , but this did not work. So I set everything back to its default. At that time I did something wrong. 

Frontend is working fine - backend allways 404 Page

PW Version 2.7

As I said: Very stupid. Any suggestions???

Thanks alot!

Edit: Helped myself by restoring a database backup ...

Thanks everyone for help and explanation.

Everything is working fine with ready.php!

So I will use this for my ppurposes...

Thanks netcarver  -  this works! 

Cann you please give me a little explanation about the differences between admin.php and ready.php.

Because on "https://processwire.com/api/hooks/" I found this:

if you are defining hooks specific to the ProcessWire admin, you should 
define them at the very top of the /site/templates/admin.php. 

And that is what I tried to do - adding functionality to admin pages ...

Hello,

I am new to hooks... - so help is very appreciated!

Found a lot of examples for hooks but not for hooking from the site/templates/admin.php.

What would be the right syntax - for example i have tried this at the top of admin.php:

$page->addHookAfter('render', 'testFunction');

function testFunction($event){

		// add a "Hello World" paragraph right before the closing body tag
		$event->return = str_replace("</body>", "<p>Hello World!</p></body>", $event->return);
}

But nothing happens.

Also tried it with wire()->addHookAfter('Page::render', 'testFunction');

What is wrong??
Thanks for helping!

Very appreciated!

Sent you  PM ...

I am very new to PW - so perhaps I am thinking/doing something wrong very basicly.

Thanks!

Hello and thanks for reply!

So again...

Module

User:

Hometemplate:

And the name of the "projekte" page is really "projekte".

Tried it even with another role and template name. Always the same: The permissions to the user are the same for all the pages.

Anny ideas??