Juergen

Hello tpr, thanks for your help! I got it working with this code: <script> $("#mainlogin-form").on('submit', function(e){ e.preventDefault(); $.ajax({ type: "POST", url: "<?php echo $pages->get('template=login')->url;?>", data: $("#mainlogin-form").serialize(), success: function(data){ window.location.href = "<?php echo $pages->get("template=profile")->url;?>"; } }); return false; }); </script> For all others who are interested in: First step: I prevent the page reload with e.preventDefault() - this is necessary to prevent the reload, otherwise you will not get logged in Second step: I made a Ajax request to my login template, where the form will be processed (validation stuff, login process,...) url: the url to my login page data : serialize all the form inputs that should be sent with the Ajax request. success: if all is alright then force a redirect to the profile page Best regards

Yes you are right. Now I understand it a little bit better. The page reload takes place after pressing the submit button of the login form - this is the reason for the page reload. But it seems that the the form will not be validated on the serverside, because the login process doesnt work. I will take a closer look at what happens after pressing the button. Thats what i do not want - I will dive more into Ajax because I start loving it

Hello tpr, if I press the login submit button from the ajax loaded page the page I am actually on will be reloaded (not the page inside the modal). Its my first attempt with ajax and login so I dont know how to get a success message from the ajax loaded login form.

Hello @ all, I use a login form which can be loaded via ajax from every page in a bootstrap modal or it can be reached directly with a link to a login page. My problem ist that the login and the redirect doesnt work in the modal, but it works on the login page (with the same code). Is there a special way necessary to login from an ajax loaded login form. As you can see the user will not be logged in and not redirected to the profile page. Maybe someone has done something similar and struggled with this problem too. Best regards

Works as far as I have tested it as expected on PW 3.29

It would be great to add this to the module with the opportunity to select if you want to use it or not (in the field settings).

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