cst989

Just fyi this breaks a bit if you put a description for the fieldset and also tick the box. Maybe just in the latest version of PW

I know this was asked before but I still don't fully understand, why does this module open a popup with a tab where you can select the target, if it doesn't do anything? I handed over a CMS using this field to a third party and they tried to use target="_blank" from the attributes tab of this field all over the site and were surprised when it did nothing. Wouldn't it be better if this module stored an object with these bits in, returning the link by default? Either that or at least drop the attributes tab from the popup if it doesn't do anything.

I hit a back-end error with a default value on this module Basically I set the default opengraph image to an image within a pagereference field, like so: {banner.image} This works fine if it exists, but if it doesn't, it hits a fatal error

Hi Erik, I would try the decimal fieldtype linked to in Robin's post - and also you don't want to be changing it directly in the db, just changing the field type

What would you consider a good, clean way to append a list of pages retrieved randomly, with more random pages (excluding those you've got already)? Eg you start with $pages->find("template=gallery-detail, sort=random, limit=100"); You output this to your template, then you have a "load more" button. This works through ajax. Now within the ajax, you need to select another 100, but exclude those you retrieved the first time. So I'm thinking you need to post all the pages you've got already, or maybe store in a session? And then exclude them from your next find(). But I imagine that would be a bit slow, excluding 100 pages by ID? Is there a more efficient way?

Var dump returns a string but still nothing in the field... It's occurring to me now, maybe I'm misunderstanding this whole thing? Is this actually meant to be populating the html field itself? Will this still work if I'm using embed method C or D on Formbuilder? I'm trying to avoid populating this with javascript but that would be so much easier... perhaps I'll just abandon it.

Hi all, I have a simple issue with inputfield:attr() not setting a value. I'm doing this in ready.php $forms->addHook('FormBuilderProcessor::renderReady', function($e) { $form = $e->arguments(0); if($form->name != 'enquiry_form') return; $inputfield = $form->getChildByName('cart'); if($inputfield) { $cart = json_encode(wire('session')->get('cart')); $inputfield->attr('value', $cart); } }); This is lifted straight from formbuilder hooks and inputfield method specs. If I echo $cart it's definitely a simple string of json, but nothing appears in the cart field (which is a plain text field - later to change to hidden) Is there something obvious I might've overlooked here? As a side question, can anyone think of a better way to do this - add my cart to a Formbuilder submission (it's not a shop, just an enquiry) - while still storing entries easily in the formbuilder entries list.

Thank you, I finally got around to doing this. I was able to combine in || $template->fieldgroup->has('meta_description') as well, and left out the , meta_title='' so you can see them all, empty or otherwise. Only minor oddity remaining is that all the filters generated by this script load in an open position, and you get an odd js glitch when you try to close them the first time - but beggars can't be choosers!

Sorry I should've been clearer. I used the latest version, ie part of Processwire (3.0.1xx) The gifs etc were very big, memory limit was 128M I think. I can't tell you the exact size because I told the person editing the page to make them (much) smaller and reupload. Of course, I can increase the memory and decrease the filesize but the problem was more about being unable to get back into the page without uninstalling the module

In this day and age I feel like the responsive option should be enabled by default! I nearly didn't notice it. How tricky would it be to pass on parameters like ?loop=1 in the URL?

When I enabled this, a page with a rather oversized gif ran out of memory saving, and then proceeded to return a 500 on the front and back-end ?

That looks great @Robin S thanks! Would this work with ListerPro as well?

Yeah I absolutely can narrow it down in other ways, its just that if this worked I would have something I could use on any site without modifying the templates checked each time, or having this extra step to check when finishing a site. I build quite a lot of ProcessWire sites so I'm making templates more often than most! I really appreciate the input though, I will make do with what I have for now. Maybe @ryan could weigh in on this one day ?

No need to apologise I really appreciate the assistance! Is this still in custom (field=value)? My field exists in about 7/10 templates, when I do meta_title= I get all pages with or without the field.

Hi @dragan thanks for the response, I think I'm misunderstanding or doing it wrong, empty fields are now being excluded. To clarify my field is meta_title - this is what I've done As you can see it matches 14 pages but there should be 16, also the number doesn't change whether using OR or AND

I'd like a bookmark in the admin to a page list of pages that have a "meta title" field, so that you can quickly see which pages need updating. Without just limiting all the templates that have the field, I want something a bit more future-proof. Is this possible? If so how? I don't want to check if its empty or not equal to anything, as it would also serve to review what is there. I have ListerPro as well but can't see how to do it with either.

This seems like one of the nicest, cleanest methods to do this, but for me it doesn't work. I end up on this page instead The Url is /manage/settings but when I click it I'm redirected to /manage/settings/bookmarks What am I doing wrong?

I worked it out while putting the code in this post and trying to remove parts til it works. I had part of my filter like this if(isset($request)) { $filter .= 'price>=".(int) $request['min'].', price<='.(int) $request['max'].', beds>='.(int) $request['beds'].', property_type='.(int) $request['property_type']; } As it turns out, you can't put line breaks in your filter like this! They obviously didn't show up in var_dump or the browser when echoed, so I missed this.

Ok so this is a bit odd, I have actually been doing this: $properties = $pages->find("$filter"); Which is not filtering results properly. However, if I echo out $filter then manually paste the result into the find instead (so it looks more like my example in the first post), it works...?? If I var_dump $filter, it's just a string... I have tried it with and without quotes

Sorry yes, it's not that removing price<=99999.. changes the result, but that nothing changes the result except that Like you say, I am returning all properties, including type 1, type 3, blank type etc., when it should only be type 2. The limit isn't even working, it's returning all 10 properties.

Can anyone tell me why I get all results from the selected template on this search, only the max price (price<=999999) changes the number of results returned. Otherwise, all properties are returned despite there being lots of different values I'm sure its something really simple $pages->find("template=property,start=0,price>=0, price<=9999999, beds>=1, property_type=2,limit=3,sort=created")

As always I work this out after 30 mins of trying, but always 2 mins after posting on a forum ? It was because the field type must be float decimal, (see below!). Funnily enough it works fine if it's Text, until you hit a negative number. I will leave this up for anyone who makes the same mistake as me.

Hello I'm having an issue with filtering on a negative longitude value. My search filter looks like this (decimal places have been shortened for the example) $pages->find("template=skyscraper,longitude>=-0.1011,longitude<=0.0708,limit=10,sort=created"); Now lets say I have two pages, one has a longitude of 0.05, this one is found. Another has a longitude of -0.05, this one is not found, even though -0.05 is still greater than -0.1011...

Are there any plans to officially make this compatible with 3.x? At the moment there's quite a few issues. When editing the field itself, it constantly says error geocoding address. In a page containing the field in the CMS it says the same on save, and it also says "REQUEST DENIED" under the map on load. To actually place a pin requires searching and then focusing off the box, pressing return will save the page but not update the marker.

Actually when I got access to the subforum for it, the latest version from there (but not the one emailed to me when I purchased) has a module for discount codes. It is super basic though... but a good insight into how to actually set it up. I think maybe for our use at the moment, Padloper is not going to be user-friendly enough for the clients that we would hand the reigns over too. However, it is clearly a great comprehensive system that I would happily use internally or personally.