[Randy Abidin]

Hi Steven,

I’ve noticed that if I programmatically put an image in a member’s image directory at …/uploads/connections-images/member_slug. Connections does 2 things:

1. When the directory is viewed at the website front-end, Connections creates the displayed logo on the fly (first time viewed).
2. When an admin goes to Manage a member in the directory in the back-end, Connections creates a smaller thumbnail the first time that entry is viewed on the Managed screen.

I have created scripts to programmatically load Connections tables with my member’s info and wanted to verify that you are doing #1 & #2 above before I assume I only need to load an image in the connections-images section and you will do the rest!

Thanks

Randy

• This topic was modified 5 years, 8 months ago by Randy Abidin.

[Steven Zahm]

@ Randy

RE: I programmatically put an image in a member’s image directory at …/uploads/connections-images/member_slug

Please do share, I would love to see what you are doing!

RE: wanted to verify that you are doing #1 & #2 above before I assume I only need to load an image in the connections-images section

I’m guessing that your scripts are properly populating the entry’s options column with the photo/logo image metadata. Correct? If that is the case, yes, Connections will automagically creates the images it needs on demand.

Hope that helps!

[Randy Abidin]

Oops, I missed that! I do not recognize the format of the options column data. It does not appear to be a serialized array but it has a serialized array look to it.

After looking at several entry options, I believe I can create ones for my entries entered by my script.

But if there is something I am missing about this format, please let me know.

I am probably between alpha and beta on my script and would be happy to show you what I am doing in a week or two.

Thanks
Randy

[Steven Zahm]

@ Randy

The data is json_encoded() faster for PHP to do and less prone to being broken. To decode, you can use nFormatting::maybeJSONdecode( $value ) where $value is the data from the options column.

Hope that helps!

ps. if you have old data, those might still be serialized. So it would be safer to do this:

$options = maybe_unserialize( $value );
$options = cnFormatting::maybeJSONdecode( $options );

That way if $value is serialized it will be unserialized. The cnFormatting::maybeJSONdecode() will simply pass the data back unaltered if the value is not json encoded. It’ll only take action if the value was json encoded. Hope that make sense!

[Randy Abidin]

Perfect! That was the last Wufoo integration items on my list.
Thanks!
I will send you what I’ve been working on in about 1-2 weeks.

Thanks again!
Randy

[Steven Zahm]

Great! Looking forward to seeing it!

[Author]

Posts