apeisa

So cool! Thanks for sharing this!

Guys, try to keep other languages than English, PHP and Klingon on translation forums. It is little bit frustrating for us who read all unread topics.

maniqui: welcome to the forums and thanks for your feedback. I think Ryan has been experimenting with tags, but not yet fully in use. We are just learning Git If you are experienced with git / github, it would be very valuable if you (and others of course) can shed a light how the ideal workflow with releases / tags should go.

Shadow fields? They inherit everything but name/label from some other field. Thus they can be used on same template as their "parent". Not that I like it (I don't), but it would probably be one solution for this kind of issues.

One possible solution for this might be new repeating fieldtype. We have few of those already, like files, images and comments.

Can anyone confirm about 2.3 and adminbar issue? Will take few days before able to test.

You can reuse fields between templates (so you don't need different body field for each of your templates), but using same field multiple times on same template is pretty confusing concept to be honest. It's like having twins and giving them same name.

Name them this way: description_person description_job would keep them together on normal view. You also might benefit from new field tags introduced on 2.3. I am not sure I understand your concern well enough, but for me namespaces in fields sounds like overengineering and would complicate it. KISS

How did you made the transition? It might help us spot problem.

Check that site/assets/sessions dir is still writable. Those folder permissions can go wrong when moving/copying stuff. Same check for other folders in /assets/ too!

Its over 30000 already. WohOO! More massages!

Not changed anything (at least not intentional) regards undo. It might be something that needs to be enabled (plugin? setting?).

Thanks for your input Diogo Though your variation of sivutyyppi is quite an interesting one Sorry guys for delay with this. No excuses, but got pretty close zero coding time last week.

This is totally guessing, but since craft has "commercial" baked in (you buy plugins directly from the app), I assume it might have admin user accounts on their server (or something like that).

We might be interested in sponsoring Solr integration too. But also just some way to index and search pdf files would go a long way. What options we might have in that regard?

Combine page arrays, sort them and then cut?

1157 should be the id of the status page, not the project page. Assuming that project_status is page field.

Ryan, it's mysql file: http://dev.mysql.com/doc/internals/en/frm-file-format.html Might have something to do with my environment, will test more soon.

Just made pull request to update this for using ckeditor 4.1. It's automatic content cleaning is just fabulous. There might be cases (is there?) where we want to allow elements pasted that are not available from toolbar, then we need a setting for that. Still few minor quirks with image field (loses possible link when changing alignment).

good idea joss, maybe the silent death might be better here.

Ryan - when trying to rename concatenate field I get this error: Can't find file: './pw_koulutus_pwire_fi/field_fullname.frm' (errno: 2)

Usually the biggest mysterious have the simplest explanations.

This is from the Readme: So in your case try this: echo "<p>" . $repeater_item->images->eq(0)->getThumb('thumbnail') . "</p>";

Samuel - welcome aboard! Can you describe more what kind of workflow you are looking for? Is it for content or code? (These are probably stupid questions, but I am not familiar with Jekyll etc)

Ok, problems with PWImage are for the same reason - both PWImage and PWLink does work if toolbar has CKeditor native Image and Link buttons also. Need to find a way to define "allowed elements" per plugin.