Ivan Gretsky

@ryan, just tested the new page export/import module in zip-mode. I was able to move some rather basic pages with images from one installation to another. Felt like launching a spaceship. And it worked! Yahoo! Congratulations! I did not get into much testing, but spotted a bug. When using "Pages that I select" and "Pages having parents" options? I could not actually select pages. The select button appears when hoverung a page and disappears instantly not allowing to make a selection. So I had to cope with selector option. Tested on 2 computers with the same result.

Good day, @horst! Was messing with an old site of mine. I did not even remember I used pim2 on this one. And getting to use this powerful tool once again was a pleasure. Thank you for your work! I had to make a overblurred version of an image for a background. So I used smooth(255) about a 10 times in a row. That did the trick, but the code looks kind of ugly. Am I missing some shortcut way to do it in a more beautiful manner?

I am facing the same problem. Made a github issue to get more attention to it.

Thank you Ryan! Both modules look awesome! And I see use cases for both of them on sites I am working on right now. It is especially nice to see these developed in response to a community feedback made through a PW weekly poll. And this is the first reason I hope both fill be released in the core. The second is that that FieldsetGroup is such a natural and kind of even expected extension of the regular fieldset it must be valuable to many. I got my ProFields subscription anyways, but still...

The answer to the original question seems to be: // use this $config->httpHosts = array(); // instead of this $config->httpHosts = array(''); I guess the 2nd line creates an array with an empty item, not an empty array. But I still have a problem with empty httpHosts config on https sites. They just do not want to work without $config->httpHosts set explicitly.

This stuff is amazing! The built-in help videos for ERPNext are auto-generated and are always in sync with the evolving interface. Just wanted to share.

Hey, @flydev! I am sure those that are not beta testers will have most questions, so better ask us, eagerly waiting for the release, after it happens) Glad you are back here, by the way!

Good day @adrian! Tracy debugger is one of the tools I can't live without no more Thanks for supporting it! I got an unexpected behavior I can't explain. Tracy bar foes not appear on form sent (there is actually quite a lot happening processing that form). I does appear on all other pages of the site as expected though. That can cause such behavior?

Just read your comment here and found out AOS now has some profound documentation. You're a monster, @tpr! The wiki is awesome! I saw it and said to myself: "Ha, but he probably does not have changelog!" But I was wrong (and astonished)! I think the main PW repo could benefit from a CHANGELOG.md like this. Especially that there are enough of nice changes to be mentioned almost every week. Sorry for offtop))

Admin on steroids adds that functionality (among many others). Just for the record.

Great, @mel47! But I was not actually advising to add an extra field to the template. I thought it would be enough just to write $page->sizeColumn = 2; before the render call. It would add a temporary property to the current $page object, which will be passed to field template (but will not write this field to database).

When you create a new product page a reference to some tags get automatically added to the product page, right? Is it your site or you are working with some clients you did not make? What tags are added? It might be that it is done with some hooks. If so, you can check the site/modules folder for some suspicious modules and read through site/ready.php and/or site/init.php - they might be there .

Hey, @webhoes! I did not dive too deep into your code, but: I think you use $inputs instead of $input. I don't see the code for the form which has to include the select and therefore do not see the way that r_selector will ever get into the $input object. You need to sent the form to get the input parameters.

There are a couple of topics kind of about this question with working solutions: https://processwire.com/talk/topic/9675-page-field-bidirectional/ https://processwire.com/talk/topic/14689-connect-page-fields/ But there are other ways. Put page reference field on vehicle-template template and add synonyms from there. Create a separate category for vehicle groups and reference category pages from both vehicle-template and vehicle_synonym-template (do you really need 2 of them?) Add a RuntimeMarkup with some easy-to-write php finding and showing the pages you want to back-reference.

Hey, @mel47! Here is the code for the method. Seems like the 3rd parameter is to override default field value, not to provide additional variables to the template: @param mixed|null $value Optionally specify value to render, otherwise it will be pulled from this $page. Did not try this, but you probably can do this to have additional variable in the field template context: // main template $page->$sizeColumn = 2; $content .= $thanks_page->render('images', '/images_column'); // images_column.php foreach($value as $image) { echo " <article class='column is-{$page->sizeColumn}'> .... }

Hello, @Slav! Is it an admin or public frontend form? If it is accessible to the public, please provide the link - it would help a lot. If not, open browser devtools console and look for js errors there. I am asking because the screenshot does not look like stock PW admin theme.

I can guess that 403 errors are thrown by the server, not PW. Here are the conditions for that in stock .htaccess file. Maybe you named your dev site folder without the "site-" prefix?

There is a nice tool for Joomla! which seems to be free for csv export. It will probably not help you to deal with the site structure though. But I am sure you will be able to handle this manually. 175 pages is not that many after all)

Might not be the best thread for this, but as you mentioned tracy... Wanted to let @adrian know, we, his PW fans truly appreciate what he is doing promoting our beloved system.

Yep, that sounds easy. Just thought I would try out something ready-made from my favourite module-builder)

I gave you 2 more) Will check it out. But still think @adrian's module coul have a "persistent" mode as well.

Good day @adrian and everyone! I was just like @Joynal, thinking this module will generate fake data for all fields and save it in the database. Could you suggest a solution for that type of behavior? I need it to do some load testing for search functionality.

The new ProField sounds amazing! Just what i did not dream of, but would dream of if I could imagine it earlier) I can see my frontpage templates getting sooo much simpler. I am really happy (again) I got my ProFields subscription .

A. If we stay in our separate installation per site realm we still have a number of options to do what you want: Use multi-instance mode from the main site. Get data from chapter sites via web service, REST, ... GraphQL... or maybe just RSS or Atom. B. You can always go for putting everything in one installation and configuring access rights for editors with something like this or this too, but probably that'll make it only more complicated. C. Finally you can go for writing a custom frontend admin for you chapter site editors while staying in the comfort of a single installation)) But that will take some time and sweat to do. I do not know the scope and budget of your project. Might be a decision worth considering.

It seems like chapter sites are to be rather independent, though alike. So you probably would like to have them each in separate installation (with different databases). [Relatively simple stuff] To speed up the creation of a new chapter site you can develop a site profile and start each new one with it rather than from one of the default ones. But this way you will still have each site with non-connnected-to-other-sites files and will have to handle the updates to the site files separately. [More advanced further...] You can run the sites from the common core though (see here, option 1), so you will have to update the core only once for all of the chapter sites. [Try at your own risk] If the chapter site will have really the same template structure and will differ only with the database-stores content you could symlink all site/templates and probably site/modules folders to one common place. But you will still have to manage changes made in admin area one by one... [That is only for the record. Never done it myself] Or use something like this or this.