ottogal

Looking into the Dev Tools: The CSS rules for #topnav say position:absolute for some screen witdths and position:static for others. The breakpoints are defined by min-width or max-width, a bit confusing... Best would be to have always #topnav{position:static}.

In my case it's independent of the scaling factor: the same at all zoom levels. So that seems to be a real problem of Fx...

Using the newest version 60.0.1 (64-Bit) of Firefox (and already in preceding versions) I get the menu rendered wrongly (see first attached screenshot - Windows 10 on a 1920x1080 screen). So the item Modules (or Forums) is not accessible, a click would activate the search input field. With the Developer Edition of Firefox all is fine (second screenshot). Can someone confirm this observation?

Your pessimistic impression of programming help forums is explicable just because it's your very first post in this community. Stay here, and you will soon have lost your prejudice... ?

Uups - I should have known I missed something obvious: I forgot to click the move button before dragging... Stupid me. Thanks for the eye opening gif!

Hi all, already since several version upgrades there is no longer the option to trash a page by dragging and dropping it onto the Trash page. But when you open the Trash you always see the (now erraneous) hint:

@tpr Thank you for looking into it. It's not such a big issue to waste time on it.

Given that {$lendoutpage->tool} is a page ID, I think you'd need {$pages->get($lendoutpage->tool)->title}

Thank you, that helped. Unfortunately I love the default theme...

Hi all, on a fresh PW 3.0.98 installation using Default Admin theme and site-default profile I have installed AOS 1.9.4 as the only site module. Two observations: (1) When in PageListTweaks I check Always show pagelist actions, in the page tree there are no line breaks any more between the entries - see attached screenshot. How do I get them back? (2) Having checked Sticky header in Admin tweaks, when on the settings page of the module I click the cog of a Submodule, the sticky header would overlay the top lines of the options of the chosen submodule. Not big problems - many thanks for this incredibly useful module!

To get a page you'd need $pages->get('name=foo')

Consider CanIUse.

No chance to make the customer read it, too?

In the Add Module From Directory dialogue I inserted the class name TextformatterHannaCode and hit the button Download and Install. The installation worked well. When I look for updates of the TextformatterHannaCode module, there is the message Session: Current installed version is already up-to-date. But not so trying to update the ProcessHannaCode module: I get the mentioned error message.

Isn't there anyone observing that same behaviour?

Have a read here: http://daily.unitedlanguagegroup.com/stories/editorials/inside-design-language-selector-no-flags

After having freshly installed HannaCode and Hanna Code Textformatter I encounter the following issue: When, in the Module Settings for Hanna Code, I click on "check for updates", I get the following error message (at the top, in red): What's going wrong? (BTW: already on PW 3.096, but I think that doesn't matter.)

From the API Reference page for WireArray class:

I'd try this: $out .= "<img src='$image->width(500)->url' />";

Shouldn't that be if ($m->template->name == "pressespiegel"){ ?

No idea - just the observation that the result is the same when you use $pages->find() with the $options parameter like this: $options = array('findIDs'=>1); $homes=$pages->find("has_parent=1", $options); echo $pages->get($homes[0])->name; //returns 'home'

Maybe you can find some useful hint in this thread: Page reference field selection based on another field

It's a principle of the page tree organisation in PW that all pages have to be children of one single root page - it's title is Home by default, but you may change it as you like. If you like to send your site visitors to a certain page in the tree, you can redirect to it. It just cannot have the title Home, so use Start or whatwver seems adequate. Another question is if this redirecting leads to a good user experience. The visitor normally would not expect to land on a subpage. I'd rethink the tree structure.

I really would hesitate to use or propagate the use of disqus. Some links: The Hidden Price of Using Disqus Why I killed Disqus Commenting on my site You can easily find more worth considering...

@AndZyk I completely second what you're saying. What's most appealing with ProcessWire is (was?) its independency of third party assets...