Jump to content

theFisher86

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by theFisher86

  1. I'm having trouble getting this working.  I'm not sure if I installed it correctly or am using it properly.

    My images are in a structure like this 

    Home
    -Images
    --Image Category 1
    ---Image_a
    ---Image_b
    ---Image_c
    --Image Category 2
    ---Image_d
    ---Image_e
    ---Image_f

    My Images are in their own specific template (called images) which contains an image field, a category field and a description field.  I want to create a generic fieldtype call img_picker which will allow the user to pick an image from any of the categories for placement on any page and I would like to use PageListImage Label to display them. 

    I can't figure out which field I should be adding to which 'label' field.  Also, not quite sure which label field you're talking about in your instructions.  Please Help!  :frantics:

  2. I like Ryan's take on that problem, because it seems flexible and clean. The only issue is that the client or CMS user won't be able to see the image he needs, o even worse, won't be able to find it if there's not a descriptive page name. I've been have the same issues that @suntrop describes. I think some kind of visual queue would be more user friendly.

    The thing is PW won't guess anything about what's in you page (that's great) so it won't classify or make a distinction between a regular page or an image page. This falls somehow short in this kind of situations where you want to select an image page from an assets parent page and it will be hard (for the CMS user) to find it based on a select or text string.

    Maybe this kind of usage needs another kind of input field. Instead of an asmSelect (and multiple select), there could be an assetSelect, which could display images or uploads to a page in a modal window. Kind of what know Wordpress is using when selecting images attached to a post. I guess this doesn't contradict PW treatment of the data, but enforces the input field concept, which is more presentational and imposes a way of displaying/selecting data. From the distance this would look like an assets manager, but instead the input field turns any page into a an assets manager, without changing any data.

    Is this making any sense??  

    Did anything ever happen with this idea as it's exactly what I'm looking for.  The lack of an asset Manager is the biggest detriment to PW in my opinion.

  3. Is there a tutorial anywhere on how to go about building custom color sets for Reno that will survive updates?

    I've 'Find-and-Replaced' colors in the original Reno color themes under the /wire/ folder which I know is a big no-no but i haven't figured out how to do it another way?

    Basically I found the /wire/modules/AdminTheme/AdminThemeReno/styles folder and just want to be able to build my own styles .css files that will be recognized by Reno.  What's the best way to go about this?

×
×
  • Create New...