Zeka

Hi.

Just curious is it normal behavior of "clone this item" in repeater field? 

As you can see this small popup doesn't close after cloning of item. I have to save a page to have the ability to work with content. 

Have you declared namespaces in your templates files? 

@cosmicsafari

Could you share your code which produced this warning?

I not sure and even didn't test it, but you can try to use 

$field->set('parent_id', '1084');
$field->set('template_ids', '[74]');
$field->set('findPagesSelect', 'test=somevalue');
$field->set('findPagesSelector', 'modified_users_id=40, status=hidden');

@Pixrael nice done!

Quote

hide button doesn't seem to toggle the class now

Yes, that normal behavior in this case, because ($this) refers to the object (button, anchor) that was clicked. 

There is working example

pen

$(this).closest(".card-footer").siblings(".card-reveal").toggleClass("show");

Hi @dreerr

There is a module that lets you control whether multi-language support is enabled at the page / branch level, but it I don't think that it is exactly what you are looking for, because it disables all language for restricted pages / branches. 

But it can be a starting point. Maybe @adrian could say is it possible to tweak his module that you can select which languages are allowed for a specific page.

I would prefer module because it's more PW way. 

It worth to mention that there is WireMail module that handles sending of email in PW. Also, there is WireMail SMTP that extends mentioned class.

You can go with a similar approach: create a module that will extend WireMail class by hooks where you can specify some specific things from your custom mail class.

Hi @webaff

• multilingual
• about 400 files at launch, scalable up to 10000 files
• files are typically PDF but can be of other files types
• front end user login with forgot password function
  • https://modules.processwire.com/modules/frontend-user/ or custom solution 
• nice to have: front end user registration
  • https://modules.processwire.com/modules/frontend-user/ or custom solution 
• 3-5 user roles for access control on page level (each file can be accessible for users of all roles or just for users of certain roles)
• login history
  • https://modules.processwire.com/modules/process-login-history/ or a custom hook probably for ___loginSuccess
• files must not be accessible by direct link, of course. Would be nice to store them outside the http-root.
  • https://modules.processwire.com/modules/fieldtype-secure-file/

Hi @Gazley

I think that it is not mainly related to CMS, but how you implement your front-end. 

There is markup src set module that you will probably find useful

https://modules.processwire.com/modules/markup-src-set/

Hi @DarsVaeda

You should specify GET or POST variables in cache settings for this template ( there is an input for this at the bottom of cache settings screen.)

Or specify * for all parameters. 

Hi @tpr

Does your module support template cache? 

Are these domains for the same site? 

You can try to use markup cache module and $cache for these pages where you have some dynamic content. 

@ttttim

I haven't done it by myself, but there is $image->sort property.

// loop over images and set new sort position
foreach($page->images as $image) {
 $image->sort = $newSortPosition
}

// sort by the field 'sort'
$page->images->sort('sort'); 

$page->save();

Hi @desbest

Hi @Marc

Not tested

$siteB = new ProcessWire($path, $url);
$siteB->pages->add('skyscraper', '/skyscrapers/atlanta/', [
  'title' => 'Symphony Tower',
  'summary' => 'A 41-story skyscraper located at 1180 Peachtree Street',
  'height' => 657,
  'floors' => 41
]);

https://processwire.com/api/ref/pages/add/

Hi @Qualtext

You can try to use ImageInterceptor, but there are no quality options in this module, so you have to modify the source of the module here and here and add a quality parameter to size method.

Hi @Chris Falkenstein

You can use markdown or textile syntax in description of fields

Hi @Thor

https://processwire.com/api/ref/page/of/

// Set output formatting state off, for page manipulation
$page->of(false);
$page->title = 'About Us';
$page->save();

Pages that you are manipulating and saving should have output formatting turned OFF.

Hi @SamC

You should allow segments for the home page and then you can do what you want.

But to keep things simple you can just rename "Misc pages" to something like "Info".

https://github.com/processwire/processwire/blob/50f2834a0ae2a9f9f2ac53439184ebdc04db2f54/wire/core/PagesTrash.php#L53

So there is id, parent id and sort position of trashed page in that name. 

Hi @ukyo

Also, you can hook save process and do your custom sanitization or validation of data if needed. 

@Robin S

Thank you for your addition.