2 hours ago, msavard said:

But seeing all the back end of Processwire will be way too intimidating to them.

Not sure what you mean here. The ProcessWire admin for non-superusers is the most minimal CMS back-end I've seen. It's just the page tree, which is easily understood even by beginners because it corresponds to the front-end structure. And from the page tree editors can only edit the pages that have the templates you allow for them.

If the page tree is still too overwhelming you customise it with hooks. If the editors only need to deal with pages in a particular branch of the tree you can conditionally set the top-level parent of the tree.

$wire->addHookBefore('ProcessPageList::execute', function(HookEvent $event) {
	/** @var ProcessPageList $ppl */
	$ppl = $event->object;
	if($event->wire()->page->process !== 'ProcessPageList') return;
	if($event->wire()->config->ajax) return;
	// If the user has the "editor" role...
	if($event->wire()->user->hasRole('editor')) {
		// Limit Page List to only show a particular page and its descendants
		$ppl->id = 1085;
	}
});

Or for more complex situations you can control which pages are "listable" individually:

3 hours ago, ryan said:

Great job and thanks for all the great modules Robin S.!

My pleasure. The hooks and inputfields APIs in ProcessWire make module development an absolute dream. It's very satisfying seeing the results you can get with just a little code, and working on modules provides a motivation to dig into the core code so I learn a lot in the process. Also, another shout out to @adrian's amazing Tracy Debugger, which has been transformative for my coding. I have several more modules in progress so watch this space. 🙂

1 hour ago, Flashmaster82 said:

Not working! I installed the latest update 0.3.3 and then the option to paste url at the image field is gone??

Sorry, I made a typo in that version. Please upgrade to v0.3.4 and it should be working again.

4 minutes ago, bernhard said:

Looks great.

Thanks.

4 minutes ago, bernhard said:

Wouldn't that be worth a PR?

That's an unknown. It's not worth the time of making a PR if Ryan doesn't want it as a PR. When it's a module I and everyone else can use it right away. When it's a PR then it's something that maybe becomes usable someday, maybe not...

https://github.com/Toutouwai/InputfieldDependencyHelper
https://processwire.com/modules/inputfield-dependency-helper/

You probably want to exclude by template for the "Link to URL" autocomplete field too.

// ProcessPageEditLink > Link to URL: exclude pages by template
$wire->addHookBefore('InputfieldPageAutocomplete(name=link_page_url)::render', function(HookEvent $event) {
	$inputfield = $event->object;
	$exclude_templates = ['basic_page', 'movies'];
	$inputfield->findPagesSelector .= ', template!=' . implode('|', $exclude_templates);
});

// ProcessPageEditLink > Select Page / Select Child Page: exclude pages by template
$wire->addHookAfter('ProcessPageEditLink::execute', function(HookEvent $event) {
	$exclude_templates = ['basic_page', 'movies'];
	$css = '';
	foreach($exclude_templates as $template_name) {
		// Hide the page list item (and its children)
		$css .= ".PageListTemplate_$template_name, ";
		// Or just hide the "Choose page" button, if the child pages should remain selectable
		// $css .= ".PageListTemplate_$template_name .PageListActionSelect, ";
	}
	$css = rtrim($css, ', ');
	$css .= ' { display:none !important; }';
	$event->return .= "<style>$css</style>";
});

@mel47, my fault, there are two bundled modules and I forgot to update the version number of one of them. Plus there was a problem where GitHub didn't pick up the casing change of a subdirectory. If you upgrade to the newly released v0.3.2 it should be fixed.

2 hours ago, mel47 said:

VerifyLinks 0.2.2

Please upgrade the module to the latest version and let me know if there is still a problem.

@szabesz, this is the support thread for Logs JSON Viewer but I think you are talking about the Custom Logs module.

Custom Logs is working for me here with a log named "my-log", so it would be good to find out why it's not working for you. Do you have a custom log named "my-log" defined in the module config? What do you see if you use Tracy to do this...

bd($name, "name");
bd($custom_logs, "custom_logs");

...just before this line.

@joe_g, you might be interested in this recently released module:

Suggests alternative words for a given input word.

This can be useful in a website search feature where the given search term produces no results, but an alternative spelling or stem of the term may produce results.

The module has two methods intended for public use:

1. findSimilarWords(): this method suggests corrected spellings or similar alternatives for the given word based on words that exist in the website.

2. stem(): this method returns the stem of the given word, which may give a full or partial match for a word within the website.

The module doesn't dictate any particular way of using it in a website search feature, but one possible approach is as follows. If a search produces no matching pages you can take the search term (or if multiple terms, split and then loop over each term) and use the module methods to find alternative words and/or the stem word. Then automatically perform a new search using the alternative word(s), and show a notice to the user, e.g.

Your search for "begining" produced no matches. Including results for "beginning" and "begin".

This method creates a list of unique words (the "word list") that exist on the pages and fields that you define, and compares those words to a target word that you give it. The method returns an array of words that are sufficiently similar to the target word.

For multi-language sites, the $user language determines which language populates the word list.

The method ranks similar words by calculating the Levenshtein distance from the target word.

Where several results have the same Levenshtein distance from the target word these are ordered so that results which have more letters in common with the target word at the start of the result word are higher in the order.

$target (string) The input word.

$selector (string) A selector string to find the pages that the word list will be derived from.

$fields (array) An array of field names that the word list will be derived from.

$options (array) Optional: an array of options as described below.

• minWordLength (int) Words below this length will not be included in the word list. Default: 4
• lengthRange (int) Words that are longer or shorter than the target word by more than this number will not be included in the word list. Default: 2
• expire (int) The word list is cached for this number of seconds, to improve performance. Default: 3600
• maxChangePercent (int) When the Levenshtein distance between a word and the target word is calculated, the distance is then converted into a percentage of changed letters relative to the target word. Words that have a higher percentage change than this value are not included in the results. Default: 50
• insertionCost (int) This is an optional argument for the PHP levenshtein() function. See the docs for details. Default: 1
• replacementCost (int) This is an optional argument for the PHP levenshtein() function. See the docs for details. Default: 1
• deletionCost (int) This is an optional argument for the PHP levenshtein() function. See the docs for details. Default: 1

// The input word that may need correcting
$target = 'dispraxia';

// Get the Search Corrections module
$sc = $modules->get('SearchCorrections');
// Define a selector string to find the pages that the word list will be derived from
$selector = "template=basic-page";
// Define an array of field names that the word list will be derived from
$flds = ['title', 'body'];
// Optional: override any of the default options
$options = ['maxChangePercent' => 55];

// Get an array of similar words that exist in the pages/fields you defined
// The return value is in the format $word => $levenshtein_distance
$results = $sc->findSimilarWords($target, $selector, $flds, $options);

Example result:

This method uses php-stemmer to return the stem of the given word. As an example, "fish" is the stem of "fishing", "fished", and "fisher".

The returned stem may be the original given word in some cases. The stem is not necessarily a complete word, e.g. the stem of "argued" is "argu".

If using the stem in a search you will probably want to use a selector operator that can match partial words.

$word (string) The input word.

$language (string) Optional: the language name in English. The valid options are shown below. Default: english

• catalan
• danish
• dutch
• english
• finnish
• french
• german
• italian
• norwegian
• portuguese
• romanian
• russian
• spanish
• swedish

Alternatively, you can use the ISO 639 language code for any of the above languages.

// The input word
$word = 'fishing';
// Get the Search Corrections module
$sc = $modules->get('SearchCorrections');
// Get the stem of the word
$stem = $sc->stem($word);

v0.3.0 released, which adds some new features such as Custom Search Builder in the datatable, a new "Error responses only" view, and the ability to exclude links from this view by defining URL prefixes, to exclude domains known to give false-positive error responses. See the updated readme for more.

A new page needs to be saved before you can add files or images to it. So try saving the new repeater page after you create it:

// ...
$contentRepeater = $page->content->getNew();
$contentRepeater->save();
// ...

I suggest you install TracyDebugger because it would have shown you a error message that explains the problem when you tried to add a file to an unsaved repeater page.

@monollonom, the edit button sounds like a generally useful feature so I've built an option for this into v0.3.0. There is also a hookable InputfieldSelectImages::getImageButtons() method if you want to add to or replace the button markup.

@mel47, the module itself doesn't impose any limit on how many selectable images you can have, but I think it would be poor usability to have more than about 100 images to wade through.

I don't see anything wrong in your hook code, so if it's timing out perhaps you are returning a very large number of images. The inputfield uses the standard admin image thumbnail, so if you have added images to a page using the API rather than in Page Edit then it can take a while to generate the admin thumbnails the first time they are rendered.

Probably you should work out a way to present fewer images for selection. For example, you could have a Page Reference field on the page to select a particular meeting page, and then the Select Images field would only show the images on that meeting page.

$wire->addHookAfter('FieldtypeDynamicOptions::getSelectableOptions', function(HookEvent $event) {
	// The page being edited
	$page = $event->arguments(0);
	// The Dynamic Options field
	$field = $event->arguments(1);
	
	if($field->name === 'image_selection') {
		if(!$page->selected_meeting->id) return;
		$options = [];
		foreach($page->selected_meeting->images as $image) {
			$options[$image->url] = "{$image->basename}<br>{$image->filesizeStr}";
		}
		$event->return = $options;
	}
});

10 hours ago, TomPich said:

I need to retrieve data from an external database (I’m okay with thay), something like an array of id => value.
I’d like the select options to show the value, and then store the pair id / value in the field.
Can I do that with this module?

Yes, you could do that. The fieldtype just needs an array of options returned from a hook to FieldtypeDynamicOptions::getSelectableOptions() and there are no constraints on how that array is generated.

The fieldtype only stores the value, but if you needed to look up the label that goes with a value you could just run the same code that generates the options array and then get the label for any value. One way you might do this is via a method for a custom Page class that returns the selectable options - that way you don't need to repeat any code. So you would add a method like getDynamicOptions() to the Page class that the Dynamic Options field is used with.

Your hook would then be:

$wire->addHookAfter('FieldtypeDynamicOptions::getSelectableOptions', function(HookEvent $event) {
	// The page being edited
	$page = $event->arguments(0);
	// The Dynamic Options field
	$field = $event->arguments(1);
	if($field->name === 'your_field_name') {
		/*
		 * Get an array of options as $value => $label from the custom Page class method
		 *
		 * If you have more than one Dynamic Options field on the page that you need
		 * to distinguish between then you could pass the field name as an argument to the method
		 * e.g. $page->getDynamicOptions('your_field_name')
		 * */
		$options = $page->getDynamicOptions();
		// Set that options array as the event return
		$event->return = $options;
	}
});

And to look up the label for the selected option in the template file:

// Get the label for the selected option
$options = $page->getDynamicOptions();
$label = $options[$page->your_field_name];

This assumes your field is for single options. If it's for multiple options then you would loop over the field value and look up each label from the $options array.

5 hours ago, BrendonKoz said:

The ProDevTools module of User Activity is another possible option.

To expand on this, these two User Activity options (marked "experimental") would be useful for this case:

You could also try Lister Selector: https://processwire.com/modules/process-lister-selector/

@Reeno, I've added multi-language support in v0.2.0. Please upgrade and let me know if you strike any problems.

Something like this:

$i = 1;
foreach($page->my_repeater_field as $item) {
	echo "<div id='slider-layer-$i'>Layer $i</div>";
	$i++;
}

2 hours ago, elabx said:

Does setting the default value in the field setting help you to set the default selection option? (I am specifically using Radios input)

I haven't tried that before, but I just tried it now and it does work. For "Default value" you have to enter the value of the dynamic option rather than the label, and the field has to be "Required" as per the default value note.

P.S. I just released v0.1.8 which fixes a minor config fields bug, so you might like to upgrade.

3 hours ago, bernhard said:

I guess your module could install Page Paths automatically, no?

I don't think it's good to automatically install modules that aren't bundled as part of the module repository. I believe PagePaths does impact some core functionality when installed (PageFinder results and possibly the $page->path/$page->url properties?) and the fact that it includes a feature to manually rebuild the paths table makes me think that it can potentially get out of sync with the page structure. So I think users need to consciously decide to install it if they want to use the Verify Links module.

I've updated the readme to mention the required modules and that they are core modules.

v0.2.0 adds a feature allowing you to force the logout of a currently logged-in user. There's a confirmation step if you click the force logout icon.

@ryan, thanks for creating this cool module!

A couple of questions:

1. Do the subfields have an ID of some sort separate to the name, such that a subfield can be renamed without losing the existing data stored for the subfield?

2. What happens to stored data if a subfield is removed from the defining file? Does the existing data for the subfield persist in the database, or does the fieldtype detect the removal and do some cleanup to remove the stored data?

Also, I think there's a typo in the blog post.

// multi-selection
foreach($page->custom_field->countries as $value) {
  $label = $page->field->label('countries', $value);
  echo "<li>$value: $label</li>"; // i.e. "USA: United States"
}

...should be...

// multi-selection
foreach($page->custom_field->countries as $value) {
  $label = $page->custom_field->label('countries', $value);
  echo "<li>$value: $label</li>"; // i.e. "USA: United States"
}

2 hours ago, MarkE said:

if the string is too long, it gets truncated in the log

LogsJsonViewer doesn't do any truncating, and doesn't get involved in the saving of log data at all - it just formats what is already in the log.

Your problem might be due to $maxLineLength in FileLog. There's a FileLog::setMaxLineLength() method, but I'm not sure how you could practically use this unless you write to your log file using FileLog::save() instead of the more convenient WireLog::save(). Instead you probably just have to try and avoid going over $maxLineLength if you are saving JSON, perhaps by doing your own truncation on individual values if they are long, before you save the data.

echo "This is the output of foo.php";

$this->wire('processBrowserTitle', 'Custom browser title');
$this->wire('processHeadline', 'Custom headline');

https://github.com/Toutouwai/ProcessRenderFile
https://processwire.com/modules/process-render-file/