Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

16 Good

About rash

  • Rank
    Jr. Member

Profile Information

  • Location
    Stuttgart, Germany

Recent Profile Visitors

868 profile views
  1. @MoritzLost This is a very elegant approach indeed! I’ve already built it in and it works flawlessly. I also appreciate it’s temporary nature that allows me to keep everything like it is, and just get rid of the helper field and the hook as soon as the select issue might be fixed someday. So another big thanks for that! (Btw: time comsumption was manageable, 5 minutes or so …)
  2. @Robin S Thank you for the information and opening a new issue. The sort option on the mentioned site is not critical, but as I work with Select Options quite often, I’m looking forward to a fix in the hopefully not too distant future. I agree to your (and @MoritzLosts) suggested Page Reference workaround – it’s one of my favourite field types, but sometimes seems a bit oversized for minor settings.
  3. @louisstephens @MoritzLost Thanks to both of you. I forgot to mention that I tried it with separated values before, unfortunately the same thing happened. In any case the db table field-direction just stores IDs so sort=direction sorts by those numbers. sort=direction.value is leading to the same error as sort_direction.title (1054 Unknown column) and sort=direction->value as well as sort=direction->title do no sort at all. I was hoping it would be just a syntax problem, obviously things are a bit more complicated …
  4. Hi, I would like to sort pages by the title of their Select Options field direction. Its easy to sort them by their option ID but not by their title. The ID’s/titles are: 1=north 2=west 3=south 4=east I would like them sorted alphabetically: east, north, south, west. What I’ve tried so far: $tracks = $pages->find("template=basic, sort=direction); // sorts north, west, south, east following the ID’s $tracks = $pages->find("template=basic, sort=direction->title); // sorts nothing at all $tracks = $pages->find("template=basic, sort=direction.title); // error: field not found If there’s no better way, I could change the select options so that ID’s and titles have the same order. Unfortunately there are quite a few pages that would need to get edited, so I’d like to avoid that. Thanks in advance
  5. Thanks a lot, dragan. You’re right, I should have specified the "where" a bit more – in this case I meant the page itself in edit mode as in your case 2. Anyway, I checked out the runtime markup field and it does exactly what I was looking for with very little effort. Perfect solution!
  6. Hi guys, I’m dealing with a problem that first didn’t even look as one, before I found out that it might not be that easy. I would like to have a link list of external sources referenced by page X. Something similar to the Page field but for external web pages and with different numbers of references. I tried to do it with a repeater field containing a text input and an URL field. That’s nearly all I want, except that I’d like it to be clickable on the admin page like so: <li><a href='URL_1'>TEXT_1</a></li> <li><a href='URL_2'>TEXT_2</a></li> The link list will be used for admin purposes only, as there are several research sources per page, that would be faster accessible than by copying/pasting URLs out of the input fields. So it’s more an admin GUI problem, as it would of course be no big thing to render a link list on the frontend. Any ideas to get that done?
  7. Hi guys, I was working with the Images Extra module for quite a while, and now I’m trying to migrate a bunch of those fields to the new core solution that came with PW 3.0.142. So far, anything is great except one thing I neither like nor understand. All custom fields corresponding with an image are stored in the filedata column like so: {"_field_1_id":"value_1", "_field_2_id":"value_2", etc.} Now some of the values store unicode escapes for diacritical characters like ü, ö, ä, ß (eg. 'K\u00fcche' instead of 'Küche') while other values of the same type are stored unescaped. Unfortunately I cannot detect any system, values from the same fields store identical values sometimes escaped, sometimes unescaped. Although the output works fine in any case, looking at things like 'K\u00fcche' slightly depresses me, so I would prefer to store all values in proper, readable characters. How could I do that?
  8. Thanks a lot, arjen and Robin S. At least my ignorance of the notes in the settings tabs is undoubtedly a bit embarrasing. But good to understand it for now and the future.
  9. Hi guys, I’m writing on a brief editor’s manual what reminds me of a topic I repeatedly stumble upon: What are the exact differences between unpublished, hidden and locked pages? Just to make it clear: There is no problem with checking or setting the status and using the result for whatever. The only thing I don’t really understand is the editor’s view: What is happening with the states beside their usage in my templates? Surprisingly, the otherwise excellent PW docs don’t reveal too much about.
  10. @Mike Rockett Fine, thank you. Just a question for future generations: As I presume that there are (or will be) several different images field types, wouldn’t it be better to keep the check more generic? The way I’ve suggested is working for me, but has the big drawback that every single field type must be explicitely listed – and you might never catch all of them. So is there a syntax for (in plain words) find('type=fields that are somehow managing images')?
  11. @Mike Rockett Thanks for your fast reply. It looks as if we’re getting closer: my images are of fieldtype CroppableImage3, resulting from the popular module with the same name. Do you think I could just change the field type where the check happens? Or extend the range of possible field types? I’m no big fan of module hacks, but in this case I could live with it. Would you mind to reveal the exact check location? Update: I’ve got the job done now – much easier than expected. Just in case somebody faces the same problem: in /site/modules/MarkupSitemap/MarkupSitemapConfig.php in line 90 I changed if ($imageFields = $this->fields->find('type=FieldtypeImage') and $imageFields->count) { to if ($imageFields = $this->fields->find('type=FieldtypeImage|FieldtypeCroppableImage3') and $imageFields->count) { to extend the range of considered field types. The option select appeared and everything works perfectly now. Another thanks for your help.
  12. @Mike Rockett This is the way I would have assumed to go, unfortunately I can't find an option like the one you describe. On the module’s config page there are the following sections: Module information Templates with sitemap options Templates without sitemap options ISO code for default languages Stylesheet Support Development Deinstall Either I’m suffering from vision defects, or the mentioned option is missing. (Or carefully hidden.)
  13. @Mike Rockett It seems as if I'm unable to include images in the sitemap. Besides that, the module is working just fine. I can find the option to exclude images (page-based) but neither the one to include them, nor do they get included automatically. I'm using only one images field in my template and the page is multilingual. Any hints what I'm doing wrong? Thanks.
  14. @Sergio A late Bingo! After a few hours of sleep I picked up your hint once more, although I still don’t understand what's going on with the hyphens. So I simply deleted the _strings.php of the translater and re-imported it. The number of hyphens appeared reduced and everything works now as expected. Another big thank you – the day is suddenly showing a much sunnier face as this little evil is defeated.
  15. @Robin S Thanks for your recommendation. I installed TracyDebugger and spontaneously I'm a bit overwhelmed (it's long after midnight here and the fights did weaken me). Anyway, it's definitely a highly interesting tool that I will examine in detail soon. @Sergio You do lot of work to help me, that’s very friendly. Your secont hint could lead into the near of a solution, as I assume a problem with paths. Unfortunately I don’t understand the relation of the path in the function and the number of hyphens the translator produces. Regarding my settings: before I tried the _strings.php method, I travelled the exhausting road of translating with __('term') file by file. That worked just fine, I only found it a bit too exhausting on the long run and started looking for a faster way (haha). So there might be something wrong with the settings, but it must be very subtile then.
  • Create New...