Jump to content

onjegolders

Members
  • Posts

    1,147
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by onjegolders

  1. Yep, I've no doubt Ryan and the most senior devs here have their very strong reasons for keeping assets so tied to pages and I very much take their word for it but from a purely dev and client point of view, I have very much enjoyed using assets in a centralised place (meaning easy reuse, it gets tiring having to drag images of the front-end to the desktop to upload them back up again on another admin page), and the bonus of being able to pass all this off to S3 or equivalent would be a huge boost for my productivity.

  2. Thanks @larrybotha, having spent a fair amount of time with Craft, I think this is one area where having files tied to pages makes things more difficult. With Craft it is possible to have you assets exclusively in say an S3 bucket, so your assets will always stay the same and accessible across environments/users

    mys3bucket.com/images/featured/featured1.jpg

    etc

    If I ever need to create a new site to access those images or a new dev needs to set up, they can just get started straight away.

    • Like 1
  3. Hi @adrian, coming to this script very very late :D

    Couple of questions, firstly, is it still usable in PW3? Secondly, I've tried implementing it but not entirely sure where the new pages are supposed to be created?

    Is this reliant on having a template "family" relationship? I have set up a page for the "Images" template and allowed only "image" template as children but not sure if I'm missing something out of the process? Thanks

  4. Hi Wanze,

    Thanks again for this module, have been really enjoying using it. Have run into a slight issue on a new site where my layout file is getting read but the views files themselves (set in `templates/views` ) aren't outputting anything.

    I have made sure that the factory module is using Twig and have tried deleting the cache but nothing is outputting from the views folder. I'm pretty sure my paths are correct. Do you have any good ways to debug? Thanks!

  5. Yeah I guess I've always liked using it as it's such a natural (at least to me) syntax, it just looks so clean.

    But you have to be able to know plain JS for sure and the definite trend is that way it must be said.

    • Like 1
  6. +1 for the future compatibility between LivePreview and RepeaterMatrix.

    For me the two go together, the possibility to allow users to create longf-orm content and build pages by adding and reordering of blocks is a great combination of power and usability (in my mind).

    Thanks again for all the hard work Ryan!

    • Like 4
  7. Hi Felix, other Twig users, I realised I posted the below in the wrong thread previously:

    Would it be possible (in theory at least) to use PW's new Page() functionality whilst still using the Twig module?

     

    I've had a fair bit of joy with most of it so far 

    {{ session.redirect('/about') }}

     for example works great. This was leading me to hope I may be able to use the full power of PW still whilst keeping things clean with Twig.

     

    Has anyone managed to do this successfully or would I have to revert to pure PHP to carry out certain PW tasks?

     

    Thanks!

  8. Hey guys, picking up an old thread here but I was interested if it would be possible (in theory at least) to use PW's $page->save functionality whilst still using the Twig module?

    I've had a fair bit of joy with most of it so far 

    {{ session.redirect('/about') }}

     for example works great. This was leading me to hope I may be able to use the full power of PW still whilst keeping things clean with Twig.

    Has anyone managed to do this successfully or would I have to revert to pure PHP to carry out certain PW tasks?

    Thanks!

  9. Hello people, hope you're all doing well!

    Just seeing if anyone has any real world experience of working with remote databases?

    Mainly in a bid to be able to keep the development process between multiple people/places that bit easier?

    I'm thinking either setting up a traditional MySQL db on the server or even using a DAAS like Google SQL / Amazon?

    Any thoughts much appreciated!

×
×
  • Create New...