hollyvalero

* Oh, yeah... I'm using these for things like moving a photo from the left side of a block to a right side, adding padding of various amounts, etc.

Okay, never underestimate the power of anxiety... this seems to work: {$page->fieldName->value}

I use the Fieldtype: Select (AKA Drop Down) a lot. And I'd be happy to switch to the Fieldtypeoptions, but I need something that allows me to create a variable, and show a human name to the user ... Something like this: left:=left right:=right The FieldtypeOptions creates this: 1:left 2:right I use them for a variety of things like choosing image effects on photos... uk-background-blend-color-dodge:=Color Dodge uk-background-blend-color-burn:=Color Burn uk-background-blend-hard-light:=Hard Light where I can add to the code: {$item->imagefx} on an image. What is the workaround for this?

Edited to say that I found the reference, deleted and it worked... but if it's worth anything, problem showed up with pw master 3.0.227 and dev 3.0.228 -- it may have been old references...

As in, it goes through the motions, but no link results. I rolled it back to 3.0.210 and I was able to link to pages, files, etc. - just thought I'd mention it.

Thanks!

This is my dumb question for the week. ? I like to clean up unneeded server files... and over time I see a few duplicates with a "." in front of the name... with duplicates below that don't have the leading dot - I assume the .dotVersion is a saved version after a more major upgrade. Should I delete the .TextformatterVideoEmbed ? Any reason to keep it?

thank, you, Ryan!!!

While I was looking for a workaround to my MarkupSimpleNav borking over multiple items separated by a pipe: 'selector' => 'template!=home|blog|category' I did an update of a production site and found a similar problem with: $features = $pages->find('template=post|articleblog, limit=1, sort=-date'); Which makes me wonder if this is a pagefinder.php selectors problem and not markupsimple nav? Everything in this installation was 100% up to date EXCEPT the (Dev) upgrade and when I updated that, this OR-condition not supported showed up.

Hi, this used to work when using MarkupSimple Navigation - trying to omit certain pages so "Blog" would appear in the top menu, but there wouldn't be a dropdown menu with endless posts... $treeMenu = $modules->get("MarkupSimpleNavigation"); $rootPage = $pages->get("/"); $options = array( 'current_class' => 'current-menu-item', 'has_children_class' => 'parent', 'max_levels' => 2, 'outer_tpl' => '<ul id="main-menu">||</ul>', 'inner_tpl' => '<ul class="sub-menu">||</ul>', 'item_current_tpl' => '<strong>{title}</strong>', 'selector' => 'template!=post|glossary|category' ); echo $treeMenu->render($options, $rootPage); // render menu EDIT: Played around a bit with this, and it does work with one template as the divider | is what is causing the problem, so this works and if you have only one template that needs this, you're set. 'selector' => 'template!=bloghome' Second edit: I think this was triggered by DEV update 3.0.183 - so this should fix itself, but leaving this here in case anyone has a similar problem....

What I am trying to do: On a blog post page, I am adding a small snippet at the bottom that has the 2 most recent blog posts by the current page author, excluding the blog post title that we are actively reading. That part works... // if this page has an author listed, s/he becomes the active $author and this page is the $activepost if ($page->cbpage2->id) { $author = $page->cbpage2; $activepost = $page->title; // Get the posts... $articles = $pages->find("template=post, cbpage2=$author, limit=2, title!=$activepost, sort=-cbdate" ); // and then format the results for each found... foreach ($articles as $article) { echo "..."; } One author post had a comma in the blog post title which broke this, and I assume this needs to be santized because I reference title!=$activepost this didn't work... $articles = $pages->find("template=post, cbpage2=$author, limit=4, title!=$activepost, sort=-cbdate" . $sanitizer->selectorValue($title)); I assume I have to sanitize BEFORE: $pages->find since it's dragging in the comma, but since I have the $activepost = $page->title; No method I've tried seems to be working. Rather than tell everyone "don't use commas!" I'd love to figure this out, but coming up with tragic results like: $dirtyarticles = $pages->find("template=post, cbpage2=$author, limit=4, title!=$activepost, sort=-cbdate") $cleanarticles = $sanitizer->selectorValue($dirtyarticles)); and that sure isn't right... ?

@Robin S - thanks! That worked beautifully.

I've been using this approach for just what you mentioned... shortening blurbs and tucking them into a page with several other items of like type... but this works great but launders out numbers... So something like "Average temperature data for each month from 1880 to 1990 to is displayed"... Comes out as "Average temperature data for each month from to to is displayed"... I see a code mention of mixed, for a mixed string, but can't figure out how to incorporate it...

EDITING TO ADD FIX: after comparing the two installations, one had Hannacodehelper still installed - so I deleted that and it's working just fine now. I have a website with a lot of charts in Hanna Code snippets. When trying to edit pages, getting a big fatal error - which is new. When I installed this it was working fine, so something since then seems to have triggered it. Fatal Error: Undefined class constant 'DEFAULT_OPEN_TAG' (line 111 of site/modules/HannaCodeHelper/HannaCodeHelper.module) - everything is up to date - PHP version is 7.3 - compiled files cleared - cache cleared Error log in PW says: Fatal Error: Undefined class constant 'DEFAULT_OPEN_TAG' Line 111 of /site/assets/cache/FileCompiler/site/modules/HannaCodeHelper/HannaCodeHelper.module Referring to: // basic settings $data = $this->modules->getModuleConfigData('TextformatterHannaCode'); $openTag = isset($data['openTag']) ? $data['openTag'] : \ProcessWire\TextformatterHannaCode::DEFAULT_OPEN_TAG; $closeTag = isset($data['closeTag']) ? $data['closeTag'] : \ProcessWire\TextformatterHannaCode::DEFAULT_CLOSE_TAG; Front end is working fine, and overall backend is accessible. Any clues?