How to create decent image thumnails

[animaux]

I get this done with quite a bit of hassle. What is the textbook-way to do it? You mention predefined selector styles.

[animaux]

Jetzt hätten wir doch noch was klären können … grundsätzlich geht’s nun.

reflection field expresion: <img src='{root}/image/2/40/40/5/{entry/datei/filename}' /> {entry/titel}<br/><em>{entry/datei/filename}</em>

Using this reflection field fork mentioned here. Is there a way to get values for $root or $workspace without resorting to this fork? Would be bad if one had to use absolute URLs, especially when using a development server.

Only slight layout problems:

[nilshoerrmann]

Actually I thought both variables were available already. Hm.
If not, why not ask @andrewminton to send a pull request to the main Reflection field repository?

I'll have a look at the image margin.

[nilshoerrmann]

The styling should be fixed.
If you are using a layout with two lines, an image size of 35 works best.

[animaux]

Looks good, cheers!

Not sure where to post this, List view is still borked though (I might as well turn that of, as it is of no great use):

[nilshoerrmann]

Well, that's not exactly an issue of this extension, but of Association Field: it just displays the markup of your Reflection Field.

That can be solved by either changing the output of Association Field (not good in my eyes), by adding styles to Association Field or by adding custom styles with Admin CSS Override.

[animaux]

Ok, thanks Nils.

[nilshoerrmann]

Personally, I'd say using a custom CSS override might be the best because the index content really depends on the project's needs. But we should discuss this on the extensions' repo.

[andrewminton]

Gents, Alex mentions above the potential issue of absolute URL's in the thumbnail views.. Even if we add the Root and Workspace constants as output nodes in the XPath, we'd still have to re-save all of the entries that include the Reflected constant no? i.e. moving servers would make no difference if using constants from Xpath cos the refleciton field makes the changes upon save.. they are not dynamically loaded..

Is it worth considering a JS solution for root and workspace from the Symphony Environment Variables here somehow?

I've sent a PR with date and constants to the integration branch for now anyways.. my forks has hashing of the reflected content in there which I need to strip out so I just patched it in the browser for now.

[nilshoerrmann]

Why not make the Reflection Field evaluate $root and $workspace just in time (= not during saving but while displaying content)?

[animaux]

@nilshoerrmann @andrewminton brill! I’d say go for that.

[animaux]

(resaving shouldn’t be a problem though using the resave_entries extension)

[andrewminton]

@nilshoerrmann That's what I was thinking. A bulk resave using resave_entries is also a neat way but wouldn't it be great to not need to worry about that when moving from a Dev to Live environment.. these things are very easily forgotten in the excitement of the switch to live.

[animaux]

wouldn't it be great to not need to worry about that when moving from a Dev to Live environment

Absolutely!

[nathanhornby]

+1 I loathe static references (shakes fist at Redactor)

[animaux]

Still display issues with the reflection field caption and edit icon:

[nilshoerrmann]

Reintroduced by aed1929.

[animaux]

Is the background supposed to be white now, or is there some leftover css fussing this over?

[nilshoerrmann]

Single selects are supposed to be white because search and select share the same area.

[animaux]

Ok, great!

[animaux]

Ok, I have a no-quite-so-dirty solution for the slightly complicated usecase of optional images … @nilshoerrmann where should we put this for documentations sake? Wiki?

[nilshoerrmann]

What about extending the readme?
https://github.com/hananils/association_ui_selector#custom-captions

[animaux]

Ok, but I was thinking of adding an example XSLT Utility. So this could become rather longish.

[nilshoerrmann]

Well, if you think it'll become too long, let's move it to the wiki.
But from my experience, people take a look at the readme, if you're lucky. They don't look any further.

[nathanhornby]

Well, if you think it'll become too long, let's move it to the wiki.
But from my experience, people take a look at the readme, if you're lucky. They don't look any further.

There's a wiki??

[animaux]

@nathanhornby not yet :)

[nilshoerrmann]

Here: https://github.com/hananils/association_ui_selector/wiki

[nathanhornby]

I completely forgot about that Github feature! Although I was mostly making a joke about me not looking any further than the readme 😊

[nilshoerrmann]

We are Germans. We don't understand jokes. Sorry.

[DavidOliver]

German Comedy Ambassador, Henning Wehn

[nilshoerrmann]

You see.

[andrewminton]

Hahah! Henning is an awkward genius :).. Serious note.. what's a WIKI?

[nathanhornby]

Haha @DavidOliver @nilshoerrmann

[animaux]

Wenn ist das Nunstück git und Slotermeyer?

Ja! Beigerhund! Des oder die Flipperwald gersput!