teppo

I've had reporting this issue on my todo-list for a while.. current behavior is obviously a bit off, as there are quite a few situations where you want to allow positive numbers or a zero

Sounds like you're looking for $config->paths->site.

@choppingblock: just like the exception says, '%=' isn't implemented with page type fields, as it's not needed there. I've explained this in more detail in another thread.

I'm seeing certain similarities with another thread, http://processwire.com/talk/topic/3530-most-selector-operators-throwing-errors/. Even the exception matches that thread perfectly. There's no "*=" or "%=" with page type field (just like that exception says.) It's not a bug or missing feature either, it's just that there's no need for such an operator. With page type fields "=" simply checks if page field value contains a value, not if it's equal to it What Antti pointed out above seems to be exactly what you're after; per your description you've got products with a field "categories" and pages with one category selected and you want to find any products that include that category in their "categories" fields. In this case this should do the trick: $pages->find("categories={$page->category}"); I'd even go as far as say that if it doesn't seem to work, the issue is probably something entirely different. Just to make sure, in your original post you mentioned field "categories" for products and your selector was "category=...", is it possible that something similar (ie. misspelled field name) is the actual issue here?

Just a quick note: similar error is mentioned here, though in a slightly different context, so it might not necessarily be related to this issue at all. Still based on that thread it'd be nice to know a) which PHP version you have and b) are you using a cloud hosting platform or some other "regular" hosting, ie. typical web hotel or VPS?

Is ProcessBatcher directory directly under site/modules or is the directory structure deeper than that? Just making sure as there's a built-in limit to directory depth, though this isn't something you'll usually need to worry about. One thing you might want to try, even though checking for new modules should already handle this, is to remove all Modules* files from your /site/assets/cache/ just to make sure that module list is properly updated.

This must be one of the best ProcessWire quotes ever. Just saying.

Hi Marty, Have you seen the CMS Critic case story Ryan wrote a while back? That seems pretty extensive dive into this subject.

@FuturShoc: wire function (wire('api-var-name')) is needed outside PW template context where $sanitizer, $pages etc. API variables won't be defined. This is briefly explained in API docs too. Most commonly this affects functions, modules (where $this->pages etc. are also available) and bootstrapped scripts. There's probably something about that internal server error in your log files (PW and/or Apache) so you definitely should check those first.

Kind of pointing out the obvious, but the code Pete posted creates config ARRAY, while interrobangs approach creates OBJECT. It really doesn't matter which one you use here (especially considering that PHP array syntax isn't exactly pretty), just wanted to clarify the terminology a bit for any "OOP beginners" stumbling into this thread..

Hello there! I can't seem to reproduce this -- searching with Chinese characters works just fine for me. Could you describe in a bit more detail what, where and how you're doing this? Are you talking about search in admin, site (front-end) or..? And just to make sure it's not something that's changed (though I can't think of such a thing right now) could you please provide the version of PW installed.

Just guessing, but could it be that $urlcat is actually PageArray? Try $urlcat->first()->title instead (or change that "find" to "get".)

@adrian: dropping conversions for now sounds like a good idea. I'm most likely going to take a look at the conversion part once I get a chance, as I'm still predicting various issues within our client base, but that's definitely not a requirement for most others.

@adrian: my information was outdated, I had no idea that mp4 was that widely supported -- forget my comments about FLV Media conversion still sounds important, as in most cases our clients seem to either a) have video files they got from external source or b) something their recorder / web cam / whatever created.. and in both cases very little (or none at all) idea how to convert those to anything else. It's a shame that ffmpeg-php can't do it.

@adrian: this sounds awesome and definitely fits some of our needs just fine.. so thank you very much for working on this! Regarding ffmpeg and ffmpeg-php, I've just tested two hosts and one had both of those installed. Other host is my Linode VPS which, as expected, didn't (and shouldn't) have them yet. I don't think this kind of requirement is such a big problem really, especially since this kind of field can IMHO be most useful in slightly larger projects, where getting a proper host shouldn't be an issue. YouTube is just fine for most others. Have you seen https://github.com/CodeScaleInc/ffmpeg-php, by the way? I can't speak for it's quality as I've never tried it, but it might be worth considering as an option to ffmpeg-php. Probably not a good default though, as a PHP extension would most likely have some advantages, such as speed (C vs. PHP.) From your feature list "automated video format conversion" sounds like the most important one to me. Unless I'm mistaken, video element only takes us halfway there; visitor's browser still needs to support each video format used and thus conversion + some kind of player sounds like the best option. One system I've been working with has something similar as this, though it by default converts all other formats to FLV and then uses Flowplayer to play those -- this has been in use for years and seems like a solid option. Anyway, I'll be sure to check your code better as soon as I can. Would love to help somehow, too. Edit: almost forgot to add that having an optional, built-in player would be a nice addition. Something like the Flowplayer integration I mentioned above, so that $page->video_field->render() would simply output the player. Just saying

@Macrura: first of all, if you've enabled HTML Entity Encoder, make sure it comes in after, not before, Hanna Code textformatter. The code snippet you posted earlier works just fine for me, so I'm guessing something else is wrong.. most likely another textformatter messing with markup before it gets sent to Hanna Code. If that doesn't solve your problem, try debugging your snippet, ie. what's the actual attribute value in there.