teppo

Seems to work now. Thanks Ryan!

So it seems. Unfortunately I've no idea how to work around that problem -- I hope someone else does. You might want to check from your client / whoever manages that server if there's any chance they could fix this. OR you could always try to persuade your client to switch servers -- this kind of problem is quite likely to affect pretty much any existing CMS and many other applications, not just PW -- but quite often that's not exactly simple task either..

Sorry @pawel, my last post was pretty vague. I meant mod_rewrite -- is that mentioned in the output of phpinfo() and if it is, what are the values of http_mod_rewrite and http_redirect_mod_rewrite? Or if those don't exist, do you see _SERVER['REDIRECT_HTTP_MOD_REWRITE'] and is it "On"? IMHO document_root itself shouldn't make any difference here, unless I'm confusing something.

Sounds a lot like htaccess wasn't properly supported there. It IS supported at some level, right -- what does phpinfo() say about it?

Not sure if this would help, but have you tried setting the RewriteBase-option in htaccess? "Optional: Set a rewrite base if rewrites aern't working properly on your server."

Hello there and welcome to the forum! Just to make sure, you uploaded a fresh install package and definitely not a pre-installed site, right? You didn't install this somewhere else (local or your own server) before this? I'm asking this because it seems like PW is expecting database user, password and hostname. And that shouldn't happen unless this is an installed version. You could also try downloading new fresh package from https://github.com/ryancramerdesign/ProcessWire again, just to make sure.

@soma, actually I failed to explain this properly. It's not enough that name starts with a number, it must BE a number. As far as I can see, this seems to be caused by function "row" of MarkupAdminDataTable.module, more specificly this check: if(is_string($k)) { // Associative arrays get converted to: // Anchor Text => URL $v = "<a href='$v'>" . $this->encode($k) . "</a>"; } else { $v = $this->encode($v); } So unless I'm missing something, 123 (username in this test) isn't a string (is_string($k) === false) and because of that link isn't created (and name is dumped.) Right?

For some reason Admin Data Table breaks when you insert a row which starts with number. See attached screenshot -- link doesn't show up and instead it's URL is printed out as plain text. Screenshot is from (unmodified) admin/users, but I'm seeing same strange behavior when adding rows to custom made Admin Data Table too. So far I've tested this with 2.1 and 2.2 and I'm seeing same bug in both. Can anyone else produce this or is there something wrong with my PW installation(s)?

@diogo: used that for couple of projects, only simple stuff though. So far seems to work well and handles some stuff that PHPs built-in mail() doesn't, no complaints

I see where you're going with this and truly respect that; quite often framework is simply overkill. I guess I was mostly referring to bigger projects, where you really do need huge amounts of code And yeah, PHP has native functions for so many tasks that it's somewhat frightening. Won't go there now, that's another issue..

Individual framework components I've used in other projects include forms, database tools, i18n and l10n, authentication / authorization / session management and filters. These are all things that PW handles itself, so I don't really see much need for them anymore. Things that I do still find useful, coming from Zend Framework, are it's web and web services components, such as Zend_Feed, Zend_Gdata (Google API tools) and HTTP, REST and XML-RPC clients. Also I could see some use for it's server tools, though I do admit that I've never had to use them before @apeisa, that's a very good point, though I'd leave the "when you are not that seasoned developer" part away to keep things simple -- security experts (and common sense) have taught us that we shouldn't reinvent the wheel, even if it's fun. If we do, we're most likely going to make same mistakes that others have made (and fixed) before us. Not to mention that especially on client projects where time and money are limited a framework can lower production costs considerably and still keep quality high. Naturally all of this mostly applies to serious stuff, client projects etc. Personal projects are very different matter

@onjegolders, as a rough answer I'd say that ProcessWire provides very good foundation for an app by making content management, access control etc. trivial. Frameworks, on the other hand, offer flexibility and powerful tools if you're building something that doesn't really need / use typical CMS/CMF features and for some reason requires very highly customized access control, URL manipulation / routing, data structures etc. MVC approach has clear benefits, but don't sweat it too much; separation of concerns is what's important -- when implemented properly, you don't need to make changes to multiple places every time your UI or DB (or business logic for that matter) changes slightly. I'd recommend reading this (old but still good) post about Rails development, which (imho) summarizes benefits of MVC / separation of concerns pretty well: http://weblog.jamisb...oller-fat-model. For the record, I've never tried Codeigniter myself and don't really know much about it. I've used Zend Framework for various projects -- and will definitely keep using it whenever it's the best tool for getting the job done -- but I've heard it has somewhat steep learning curve compared to some other frameworks. I'd still recommend checking it out though: http://framework.zen...n/learning.html.

Testing it right now and seems solid. Many thanks to Ryan, this'll come in handy

Hello there, Just wanted to say that I don't think that's nuts at all! Actually, I'm planning to do something similar soon, for pretty much the same reasons - proper access control is painful to implement and PW handles most of what my app needs to do straight out of the box So far I've been planning to implement each account as a unique role, which would be the most obvious approach -- especially since in my case 1) many accounts will have more-or-less customized templates and 2) number of accounts is quite limited, so that won't become such a huge problem anytime soon. Using this method allows me to control exactly which account specific user belongs to and also allows one user to belong to multiple accounts if/when necessary, which can be quite handy. Obvious downside is that role and template lists might become a bit messy in the long run, but that's something I can live with. And like I said, that's not such a huge problem with my relatively limited scope. Anyway -- I was browsing through page-specific permissions topic (http://processwire.c...ic-permissions/) and was wondering if that could solve this problem, or at least a part of it (huge template count?)

Seems that @diogo beat me to it. That's what you get for multitasking.. Anyway @poochandy, as you can see there's more than one way to do it. Dig in and don't hesitate to ask if you get stuck!

Hello there, and welcome to the forum! What you're describing there sounds like something PW handles very well. You could, for an example, create all those sections as pages in PW and have one template file render content for all the others. Here's a post about somewhat similar concept: http://processwire.com/talk/topic/821-question-understanding-templates%E2%80%93advanced-templating/#entry6999. This way you'd create a template file for all individual sections (assuming that they actually have different markup & fields each) and then at some point, index / home page probably, render them all. Please note that I haven't done anything like this myself, but the concept doesn't seem too difficult - I'm sure others will be able to provide more helpful examples and educate us both about more sophisticated ways for achieving this result. ... actually, this sounds like a good idea for a nice little tutorial if anyone has some extra time ...

Sounds great! Makes sense. In my case this problem appeared after importing pages with ImportPagesCSV module..

Is there any way to insert file / image descriptions while importing? If not, any idea how one could implement a feature like that?

Couldn't find another topic on this, so I'm creating a new one. My idea (wish, if you wish.. no pun intended) is actually quite simple: wouldn't it make sense to enable sort order setting for templates in addition to individual pages? That way I wouldn't have to re-set sort order every time I create, for an example, a news page (which can only contain news items and thus has pretty much only one usable sort order throughout the site.) Also: current default sort value for new pages is "none", which can produce quite peculiar effects - apparently because DB itself uses some very obscure magic for deciding sort order - and I'm having hard time figuring out why anyone would wish it to act like this. As a second idea, wouldn't it be nice if default sort order was "created" instead of "none"? So - what do other folks think about these? Oh, and by the way, if there already IS a way to achieve one (or both) or ideas above, that'd be great (and in that case, sorry for the confusion!)

Antti: regarding the form builder, you might also want to check out how this stuff is handled in Form Builder Plugin for Pimcore: http://www.pimcore.org/wiki/display/PLUGINS/Form+builder+plugin. Pimcore uses Ext JS heavily for all it's views but putting that aside the basic UI concept there doesn't seem too far from what would be required here.

Thanks netcarver - had a quick look at those and it does look promising already! Please, keep up the good work -- and make this available for us "outsiders" as soon as you feel it's mature enough for that Somewhat offtopic: what you're building there kinda reminds me of Zend_Form and actually made me think about putting up a quick proof-of-concept of using that in a PW site. If not for production use, might at least be interesting to see how (and if) it works out.

So the only thing that's not working is changing the link (and link content), right? If that's the case and you only have two languages, something as simple as this should do the trick: <?php $lang = ( $user->language->name == "finnish" ) ? "default" : "finnish"; echo "<a href='./?language={$lang}'>{$lang} flag</a>";

It's obvious that stuff like this takes time -- and building multiple features, especially when they're big ones, at same time is nowhere close to a good idea -- but I just had to drop in to say that we're really, really looking forward to the form builder too. Anyway, it's always good to get a heads up about how things are going, so thanks for sharing this Ryan! I'll go check what Netcarver's been building now