Jump to content

MrSnoozles

Members
  • Posts

    71
  • Joined

  • Last visited

Posts posted by MrSnoozles

  1. On 12/15/2023 at 8:22 PM, teppo said:

    I've had for a very long time on my todo list a related idea; basically something like the https://translate.wordpress.org/ portal for WordPress.

    Yes, that's exactly what I had in mind too. Wordpress really drives me insane as a developer, but the fact that almost all the backend is in the clients language is one of the few things I envy when using ProcessWire.

    The advantage is that everyone can submit translations in a matter of seconds, when you're bored or just waiting for your train. No need to clone a repo, go through the source files and submit a PR.
    Core: https://translate.wordpress.org/locale/de/default/wp/
    Plugins: https://translate.wordpress.org/locale/de/default/wp-plugins/

     

    • Like 2
  2. 14 minutes ago, monollonom said:

    Personally I don’t really see how setting something like this would entice the community to contribute more than making a pull request

    You could be right on that. I'm thinking however that it would be beneficial for three (subjective) reasons:

    1. It's easier to see the status of translations and contribute to them from a GUI.
    2. I personally don't want to create a PR for just some of the translations. With that system you could add some suggestions here and there
    3. It would be easier for non-tech people, although admittedly most of the ProcessWire users probably are

     

    4 hours ago, bernhard said:

    Have you seen RockLanguage? There was no feedback at all...

    Haven"t seen it, but it does seem a lot easier than the core way to add translations.

    • Like 1
  3. @ryan Good points. The slim core and the enormous flexibility is why so many love ProcessWire and trust you with your decisions. Still I want to comment on one point:

    42 minutes ago, ryan said:

    As for translations of the admin, PW's admin is already 100% translatable, so if you are seeing a mixture of English and another language, then that means that the language pack you have installed is missing translations. But that's something you'd need to ask the author of the language pack about. You can also always submit a pull request to the translation author's language pack, or create your own. PW makes this all very simple. 

    I know it is simple, but the reality is that in client projects it often still ends up being a mix of <language> and English, because not all modules provide translations (the community seldom submits pull requests for languages) and there is no time to translate everything. I think that ProcessWire is lacking in this area has to do with you rarely needing it in another language but English.
    My idea how this could be improved would involve three relative simple steps:

    1. Set up a community translation tool, like Weblate (https://weblate.org/), where people that want to contribute can easily see which translations are still missing. Weblate is really good feature-wise, but the interface for adding translations could be simpler, so another tool might fit better.
    2. Write a crawler that goes through all the uploaded modules and core files, extract the translatable phrases and upload those packages to Weblate
    3. Write a ProcessWire module that maps the languages defined in ProcessWire with country codes, then automatically downloads the matching translation files from Weblate whenever a module is added or updated

     

    In general: would that something you would consider useful? If so I could try implementing a POC when I find the time.

     

    • Like 4
  4. @David KarichVery good points. I'm very excited for this feature too. IMO the things we and our clients have been missing the most in ProcessWire, apart from versioning, are (in that order):
    - global asset management / media manager with directories to reuse assets in various places. The lack of this is is often the sole reason we can not recommend ProcessWire for some projects
    - automatic backend translations using ProcessWire in any language other than English is suboptimal, because usually the backends will end up being half in <target language>, half in English
    - a proper multisite solution to handle multiple domains / channels in a single instance. The Multisite module is a good start, but having more isolated channels and sharing/isolation options for each channel would make this a much better fit
     

    • Like 2
  5. Hey,

    so I have a website with three languages:
    - Swedish (default)
    - English
    - French

    I would now like to publish some research result in English only and not translate it into Swedish and French. I'd still like to link to it from the Swedish and French versions though. How would you do this with ProcessWire?

    Spoiler

    Some additional information:

    What I would probably like to happen is:
    - When clicking on the Swedish or French version they should display the content filled in the English version
    - a canonical indicates the correct url (the English version)


    How it could be solved (but doesn't feel like a good solution):
    - add a select-field to the template where the user can choose one of a language if it's a single-language site
    - when a page has a value in thatfield a hook handles the loading of the correct language. e.g. when we're visiting the Swedish website and in the field is selected that the language is english, that hook will make the page load the English content instead of the (empty) Swedish

     

  6. On 5/13/2023 at 1:17 PM, kongondo said:

    Happy to get early feedback, thanks.

    This looks so much cleaner and easier to use than the current version. The context menu looks very nice already. The other elements could need some more polishing - I know that's not been a priority yet, still you asked for feedback 😉

    Some things I noticed on the video
    - a breadcrumb navigation should be visible to reflect the directory navigation (when you click on people it disappears, when you click on "men" it should show People > Men)
    - the selected category and parent categories should be visible (when you click the "men" category nothing is active) (it would probably look nicer to use bold text instead of green)
    - the spacings and alignments look a bit off. Some inspiration: 

    https://demo.filerun.com/?username=admin&password=admin
    and the screenshots below

     

    https://cdn.dribbble.com/users/372375/screenshots/14473793/media/94daec64a83f99c8731e320df68d4541.png?compress=1&resize=400x300&vertical=topReact UI kit for Figma — Design & Code toolkit 2-in-1 by Roman Kamushken  for Setproduct on Dribbble

     

     

    Advanced Search | Web design quotes, Web design, Web app designhttps://cdn.dribbble.com/users/971133/screenshots/15899953/media/d258260eeef2344436c1ccbc159ddc2d.png?compress=1&resize=400x300&vertical=top

     

     

    • Like 1
  7. Freaking awesome!! I've been thinking about doing the same for bunny.net these last couple weeks and the approach I had outlined in my mind would have been very similar to yours. Very well done, I'm super excited for this 😃

    • Like 3
  8. @kongondo Just want to let you know I'm super happy development on the module continues. The functionality of the current version is great, it's just a bit unpolished compared to file managers from other CMS.

    As for new features: I agree with the others, folders and simplified search (+ advanced filtering) are definitely my top two wishes too. Also easier API access to render media in the frontend would be a nice to have. If I remember correctly it was a bit more complicated to use than the usual ProcessWire API.

    Super excited for the updates, thank you!

    • Like 2
  9. 3 hours ago, bernhard said:

    Puh... I'm not sure

    Neither am I. ? It was just a thought that came while watching your video. rockFrontendEditing for example wouldn't sound as catchy, but would be clearer for newcomers.

     

    3 hours ago, bernhard said:

    I have played around with my code a little and think that that we could really simplify alfred syntax even further! 

    I really like the new syntax. I wanted to suggest a Latte attribute first, but then decided to keep it simpler. Your approach looks nice. Imo it would b good to explain why and when this is needed instead of just using $page->edit('myfield')

     

    3 hours ago, bernhard said:

    f you want to use the alternate syntax you can do so. RockFrontend is smart enough to see that you are rendering scripts/styles manually and will not inject them twice ?

    Perfect! So you get the best of both worlds.

     

    I'm sick at home this weekend, hopefully I will find time to give it a try already.

    • Like 1
  10. BOOOOOOM ???? Bernhard dropped the bomb.

    I'm halfway through the video and so far love everything about it. Nice video setup and editing there too. Going back to the video now ?

    -------------------

    Edit: Okay, I'm through and this is definitely super cool. Looking forward to trying it out. There are two things though that I'm not sure about and wanted to mention:

    1. The name Alfred. While you've found a sweet acronym it (in my opinion) has the huge drawback that new developers looking at the code and seeing

    alfred($page, ['fields' => 'gallery'])

    will have absolutely zero clue what's going on. Most of us love ProcessWire because it's intuitive. With this name you have to first learn that alfred is an inline editor to understand what the code is supposed to be doing.

     

    2. I'm not sure about this one, but adding assets to the header through hooks reminds me of dark Wordpress times. I like that with ProcessWire you are able to to see where things are coming from and you have total control over what's happening.

    • Like 3
  11. On 7/29/2022 at 10:30 PM, ryan said:

    As you can see, we're using the ProcessWire comments field to store not just the review, but also 15 other details and up to 6 photos, per review.

    Does that mean we will be able to attach images to comments? I've been looking for such a functionality for a while, that would be great. Could you share a code snippet on how to do it?

  12. Article editor is nice and much more lightweight than CKEditor. @Marcjust posted an example of how an integration could look:

    And while CKEditor might have more features in general, for editing website content I think Article offers greater flexibility and is easier to use.

    ----

    @ryanI once wanted to add images to FieldtypeComments, so each comment can optionally have one or multiple images attached to it. Is that something that could be supported too? If not, could you think of an easy way to integrate images into comments?

  13. @ryan Digging out a 9 year old topic:

    A common use case for me would be to sort users by `created`, so newest users are displayed first. Unfortunately the column `created` can not be selected in the module settings, as it's a system field. Neither can the default order be specified in the module configuration. Would that be something to consider for future updates?

  14. I've played with RockMigrations over the last week to get a better feeling of what it does.
    I didn't like the approach at first, because imo migrations should be run once to bring the system to the required state. Having them run on module refresh seems a bit too dangerous for production sites.

    I agree though, that for the sake of getting things done, your approach is very convenient. What you have planned for the next version could combine the best of both worlds:
    - a directory is added to the watchlist
    - migrations in that directory are executed in an alphabetical order
    - a hash-value for the file contents is stored somewhere when the migration is run
    - as long as the file contents does not change, the migration is not executed anymore

    That way the quick protoyping, as well a "proper" 1-file-per-update migrations could be achieved. Is this what you have in mind too?

  15. Agree with @FireWire. This looks like the behaviour is wrong and an issue should be raised in the issues repository. The problem seems to lie in this line: https://github.com/processwire/processwire/blob/d78276e2c265f6b70384a13eb4febd4811a1db77/wire/core/WireHttp.php#L563

    Every statuscode should be treated as a successful response, as long as the server was able to contact the remote server.

     

    EDIT:
    The comment on top of the line of code linked above says `no need to fallback to sockets`, but then the $result is set to false. I think this is meant to be a `$result = true;` instead of `$result = false;`. Then the rest of the logic would seem to be correct again.

    • Like 3
×
×
  • Create New...