Juergen

Hello @tpr there is a spelling mistake in the new thumbnail feature: It should be "Pagelist thumbnails" and not "Pagelist thumbmnails" Best regards

Thanks! I will try this out.

I have discovered an z-index issue with the Leaflet module. It concerns the breadcrumbs and headline div. As you can see the magnifying glass on the right and and the size changer on the left side overlap. Adding the following z-index to the breadcrumbs and headline div solves the problem: #breadcrumbs {z-index:11} #headline {z-index:11} A lower index than 11 will not work. Best regards

Thanks for this awesome module!!! Question: is it possible to remove loading the FontAwesome CSS from the LeafletMapHeaderLines (fe. at the options)? I use FontAwesome on a website and this will lead to that it will be loaded twice. Best regards

Thanks @bernhard I am on vacation at the moment , I will take a look when I am back.

Can someone give me an example code of how to initialize this module with a cron job? Do I need to create a cron job module or can I use ready.php? Thanks for your hints!

Hello Francesco, it depends on how you structure your files and directories. There is no general rule for it. Thats the best on PW because you can do all on your own. You have to include it usually in your head.inc file if you are using Joss tutorial as your starting point. The head.inc usually include all the meta data from the head section and there you can add these lines of code. If you are using Bootstrap css and js files I would prefer to load those files from a cdn (fe jsdelivr or Bootstrap CDN) instead from local copies. Best regards Jürgen

Hello teppo, I have re-installed this module on a 3.25 dev version today and it works. I dont get any error messages

Perfect! Now it works as expected. Thank you

Hello tpr, I use the latest Version (3.24) and I found out that this only happens if you have a special image grid setting. It is the last one which shows the inputfield for the title. If you switch to the grid views without the input field it works correctly. Maybe this could help you to reproduce the behaviour. If not please let me know.

Hello tpr, I am so sorry, but I found another z-index issue at the image field. As you can see the image upload field overlap the static bar at the top. I have only discovered that with the image upload field. It seems that the static part should have a much higher z-index. Best regards

What I have also discovered is a z-index issue of the tooltip icons. As you can see the icons are always visible if you scroll the page down.

Wow! Works like a charme!! The only thing I would change is the color of the bold text in the tooltipps. I dont know why but, you use #777 as color. I think the contrast between the background and the color of the bold text is not really good. Here is your CSS part: .description strong, .notes strong { color: #777; font-weight: 700; } I would use #fff for bold text too so it would be better readable. Congratulations to this awesome module!

I like the last one most!

Hello everybody I have a problem by using the page fieldtype in the modal mode. I have activated that the user can add new pages (see screenshot). After clicking the add new button I always get the message that no content can be returned. This is only if I use the modal mode. Here are my settings: I have added the parent page (called Preislisten-Kategorien), so everything should be ok. If I dont use the modal mode it works quite well, but the page is multilingual so the modal window would be the better option. PW data: I use the latest dev version I hope someone can help me out. Best regards

I dont agree with you, because it would be surely possible to check if the field is added to a template or not. If yes you will get a warning and you are not able to delete it. If the field is not added to a template you can click the deletion button. To make it more concrete: Deletion possible only for fields which are not added to a template - this information was missing on my first post.

Good idea!

Today I had to delete about 40 unused fields. I had to click on every field to get to the deletion button. So it would be great if a deletion button would be integrated in the field overview list (fe a basket symbol) which alows to delete a field directly from the list without going to the field setup.

I want to use a repeater field to create business hours (opening hours) for a shop. Each repeater item should be a day (Monday, Tuesday,....) and consist of different input fields (Inputfield time, Inputfield options,...). In this case the customer should not be able to delete or add a repeater item after I have created 7 repeater items (1 for each day) Question: How can I remove the delete or add button via a hook after creating the repeater items, so that the customer is no longer able to add or delete a repeater item? Here is for example the code for the add link at the bottom: /** * Render the repeater items * */ public function ___render() { // a hidden checkbox with link that we use to identify when items have been added $out = "\n<p class='InputfieldRepeaterAddItem'>" . "\n\t<input type='text' name='_{$this->name}_add_items' value='0' />" . "\n\t<a href='#' class='InputfieldRepeaterAddLink'><i class='fa fa-plus-circle'></i> " . $this->_('Add Item') . "</a>" . "\n</p>"; return $this->buildForm()->render() . $out; } Thanks

You are absolutely right!! This code works: $user->getFormatted('userimage')->size(75, 75, array('cropping' => 'outside'))->url; I didnt know that user fields are specific on frontend, because I never had troubles before. Thank you so much! Now everything works as expected.

Oh it seems that the size attribute in the api call is responsible for the error. This works: $user->userimage but this works not: $user->userimage->size(75, 75, array('cropping' => 'outside'))->url Settings of my userimage field: Error message with Tracy:

$user->userimage->last() This line of code is responsible for the error.

Ok I have traced the problem down to my userimage. There must be the problem. The API of the userimage seems to be wrong. If I comment out the userimage, the name of the creator will be displayed properly. So the API call as described above works also in 3.0.21.

No I dont hook into image fields. I only have a textformatter running (without a hook) which manipulates the image class of images added with the CKEditor. The callstack shows me always an error on the index.php.

Doesnt work either for me. I have tested it with Tracy debugger tool and I always get an error message with pageimage after adding the line of code to the template? Exception: Method Pageimage::last does not exist or is not callable in this context (in ........web/wire/core/Wire.php line 409) I dont know why because this has nothing to do with the user name. Maybe I have to dive a little bit deeper into my template code.