adrian

I haven't tried it, but check out this module that allows you to customize the embedded video's settings: And regarding this: " It doesn't work in combination with HTML Entity Encoder" - try changing the order of the text formatters.

Thanks for the update @flydev - I am definitely very excited to try this - thanks for the hard work!

@xavier - if you really don't know anything about programming then I have to agree with @Robin S - an AngularJS based site is not the place to start - there is so much more to consider. You need to figure out if your PW selector is getting the pages you want, and then make sure they are being returned as JSON and correctly parsed and outputted via Angular.

There have been significant changes to the File Compiler since that version. I would recommend the latest dev version - 3.0.50 It may not be related to this issue, but it shouldn't hurt!

$page->parent->podcast_show PS - have you checked out the cheatsheet? http://cheatsheet.processwire.com/

I know code syntax choices can be a personal thing, but take a look at how much simpler this version is to read: foreach($pages->find("deals_show_on_endorse={$page->id}") as $deal_item) { echo $deal_item->title; } or if you want a one liner, even this: foreach($pages->find("deals_show_on_endorse={$page->id}") as $deal_item) echo $deal_item->title; PS - not judging here, just want to make sure you are aware of other options. I am not sure if you are just new to PW or also new to PHP.

One thing I notice is that this looks like an incorrect mix of the PW PHP $page variable and the JS toJSON() method. We also don't have any info about what pw.busca() does. I know its a search, but it would be good to see some code. I have used Angular and PW together a lot, so I might be able to help here, but I honestly don't know exactly what isn't working yet.

It's weird, I was also about to start on something very similar, but also just recently noticed @rot's module, and now yours. @rot has been quiet here for a couple of months, so it would be good if he could confirm his intentions with updating his module. If you are close to being functional, it would be great to test both to figure out the differences in feature set.

@kreativmonkey - I would also recommend upgrading the to latest stable, if not the latest dev. 3.0.4 is very old now and there have been many bug fixes and especially, lots of improvements to the file compiler.

Hi @modifiedcontent and welcome to the forums. This is the seminal thread on creating forms via the API:

It seems to me that PW's sort() could support PHP's sort_flags - then you could specify something like: $pages->find($selector)->sort("fieldToSortBy", NATURAL_SORT); I just did a quick hack of WireArray.php and on first glance it all seems to work fine. The NATURAL_SORT flag does require PHP 5.4.

https://github.com/ryancramerdesign/skyscrapers2

I am on the default theme. I can't reproduce without AOS. It's not consistent, but it's also not a huge deal

The hover on the entire pagelist line feature is a little buggy. It's a little sporadic, but if you open a branch and then collapse it, the hover no longer brings up the action buttons. Let me know if you can't reproduce and I'll try to investigate.

Not sure about this - I like your thinking, but then where do I stop? Do I extend it even further to display if there is a new PW or Logs panel item? What about a new Mail panel or Page recorder entry? I think perhaps that manually triggered things shouldn't automatically unhide the bar because you know you've added the call so you will be looking for an entry on the bar. If anything I think maybe the logs panels should maybe trigger display of the bar if they are error related entries. As always though I am open to feedback if others think this change would be good.

Once you have clicked to show it, a cookie is set which overrides the config setting. Or is this because there are errors in the errors panel, which as I mentioned now forces it to display, which I think is a good idea, but can revisit/make configurable if you needs don't like it. I know I already have a lot of settings, but I feel like this might be going a little too far especially given how easy it is to toggle. It looks the same to me both front and backend. Perhaps you have extra padding on the frontend due to some css cascading down? Could you maybe post some comparison screenshots and/or debug the css to see what might be conflicting. Thanks.

@gmclelland and everyone. Latest version takes care of the hook priority issue and adds a new feature to the new hide/show toggle button. Now if you have it hidden and it detects an error it will force it to display. Once you fix the error, it will go back to being hidden again. I think this is a nice compromise for those who don't like having the debug bar visible all the time, but don't want to miss any reported notices/warnings. Please let me know if you notice any problems with this change.

Agreed it's not really always possible. RepeaterMatrix or even PageTable fields make it possible, but there is always some sort of trade-off

It works just fine on 3.x As far as I know, it's still the only option.

Any console network errors? Any 3rd party modules not up to date?

@chadamas - glad it's coming together for you. You might also find this useful: https://processwire.com/blog/posts/processwire-core-updates-2.5.14/#multiple-templates-or-parents-for-users

This sort of thing has been an issue for RTEs forever which is why whenever possible I separate headings into their own field and remove the option for users to style the text (except for bold, italics and inserting special characters and maybe sub and superscript for some sites). I know this isn't always possible, but it's always my preference.

@gmclelland - thanks for helping to track that down! I think that 100.5 priority in TemplateEngineFactory is being set automatically. I am honestly not sure the best way to approach fixing this. The most guaranteed would probably be if I manually set it to say 1000, to make sure it is after any other hooks that might also manually set the priority to a high value. I guess I'll do that for now. There are actually a few Page::render hooks used in Tracy, so I will take care of those as well because I feel like TemplateEngineFactory will be breaking those as well. Thanks again!

Thanks @webaff - this is fixed in the latest version.