New Extension: Seesaw

Wow – we have connection to one channel, I add idea of the totally the same extension in my future dev. list just 10 days ago 😊. Planning to take a time on next weekends. But nice, that I can spend time for another extensions 😊.

A couple ideas for features: 1. Cell type with template system - for possibility to use data in your own style with our modification ext.. 2. Hope that you can fined time for integrate my MX UniEditor Image something like this:

---;

forum break the source :(, so you can find example of code block in attachment

Thanks!

A couple ideas for features: 1. Cell type with template system - for possibility to use data in your own style with our modification ext.. 2. Hope that you can fined time for integrate my MX UniEditor Image something like this:

Hey Max,

Thanks for the code demo for supporting MX UniEditor Image. I don’t have a license to test this out, but if you can verify that the code you provided works, then I’ll gladly add it in.

As for your #1 feature idea, can you explain a bit more? I’m not quite sure what you mean, and don’t want to guess wrong.

Thanks for the feedback! Anything else you can think of, just shout.

Cheers

MX UniEditor is free extension 😊 About idea – is type where user can setup new column use raw information from field. For example, if user know that field has url to img, he will choose free mode and entered to format field something like this:

<img scr="{field_data}">

It will be usefully in case if field type is not supported.

About idea – is type where user can setup new column use raw information from field. For example, if user know that field has url to img, he will choose free mode and entered to format field something like this:

<img scr="{field_data}">

It will be usefully in case if field type is not supported.

Great idea Max, I’ll see what I can do. I was even thinking of allowing a php function call that gets eval()’ed, to allow for even more flexibility…

And apologies for the MX UniEditor confusion, I’d known your extension was free, but was mistaken to think the editors it used weren’t.

Thanks!

Nice work John,

This is very helpful add-on.

And it works perfect.

Looks exciting.

Produces hundreds of this error notice however:

Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /[bla-bla-bla]/system/extensions/ext.seesaw.php on line 703

And also this on the Edit page:

Notice: unserialize() [function.unserialize]: Error at offset 65530 of 65535 bytes in /home/engaging/public_html/system/extensions/ext.seesaw.php on line 640

Looks exciting. Produces hundreds of this error notice however:

Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /[bla-bla-bla]/system/extensions/ext.seesaw.php on line 703

And also this on the Edit page:

Notice: unserialize() [function.unserialize]: Error at offset 65530 of 65535 bytes in /home/engaging/public_html/system/extensions/ext.seesaw.php on line 640

Hmm. Did it through these errors after activating but before visiting the Settings page and saving them at least once? Or do they happen all the time no matter what?

I’ll tinker & test…

Produces hundreds of this error notice however:

Hi Adam,

Still working to debug this. Would you be willing to PM me a row from your exp_extensions database table? Seesaw has 4 rows in this table (find them by searching for rows with class column value of “Seesaw”, and I only need the “settings” column of any one row. The “settings” column is a serialized array. If you’d be willing to send that to me, I’d be real helpful!

So that you’re aware, it’ll contain the labels of every custom field you have across all of your channels. So only if you’re OK sharing this with me…

Also, again any info you can give me on the steps you took to encounter the errors, would be appreciated too.

Cheers! John

Produces hundreds of this error notice however:

Hi Adam,

Well I have a theory about the errors you’ve encountered, though I can’t reproduce. I’ll be updating version 0.4.6 momentarily with an attempted fix, if you have the time to update and test, it’s much appreciated.

Cheers John

John, thank you thank you, it’s such a brilliant extension. I’m using it seamlessly right now.

My only thing to add to your wishlist would be Seesaw parsing the first row of an FF Matrix field. When I attempt to display a 5-cell FF Matrix field, it does give me row #1. But I get this output:

a:1:{i:0;a:6:{i:1;s:17:"10118 - 79 Street";i:2;s:8:"Edmonton";i:4;s:7:
"Alberta";i:3;s:12:"780.450.9906";i:6;s:0:"";
i:5;s:27:"http://morangostekcafes.com";}}

It would be sufficient if it could even clean this up to

10118 - 79 Street | Edmonton | Alberta | 780.450.9906 | http://morangostekcafes.com

Anyway, thanks again!

10118 - 79 Street | Edmonton | Alberta | 780.450.9906 | http://morangostekcafes.com

Hi Oxygen,

Great idea, I’ll definitely add it into the pipeline. The whole FF Matrix thing is a bit of a pandora’s box though, I immediately think of a few different ways to represent the matrix: Pipe-delimiting the first row, a simple row count, showing just 1 particular column of the first row, (then what if that 1 column is itself an image), etc…

I could tell as I was setting things up that the simple type/format arrangement might prove quickly limiting… but I wanted to release it early for just this reason, to figure out how best to improve!

Anyway, glad it’s working for you, and thanks for the suggestion. Maybe by the New Year I’ll have time to roll out an update…

Hi John,

Thank you for a helpful extension! I Just gave it a quick try… seems to work fine with one minor exception that you might want to know about: I get a blank white page after clicking the “Save Settings” button. Settings are saved just fine. I’m running a bunch of extensions and have a fair number of custom fields. My memory_limit is currently 128M

Any chance you can integrate with the 1st party Cloner/Clone Entries extension? I’d like to be able to hide the “Clone” column on a per weblog basis. Some of my weblogs have playa and other relationship fields and cloning such entries is a bad idea since the exp_relationship table isn’t updated when cloning. Any help would be appreciated. I haven’t yet found any way to work with Cloner on a per weblog basis…

Hi John, Thank you for a helpful extension! I Just gave it a quick try… seems to work fine with one minor exception that you might want to know about: I get a blank white page after clicking the “Save Settings” button. Settings are saved just fine. I’m running a bunch of extensions and have a fair number of custom fields. My memory_limit is currently 128M Any chance you can integrate with the 1st party Cloner/Clone Entries extension? I’d like to be able to hide the “Clone” column on a per weblog basis. Some of my weblogs have playa and other relationship fields and cloning such entries is a bad idea since the exp_relationship table isn’t updated when cloning. Any help would be appreciated. I haven’t yet found any way to work with Cloner on a per weblog basis…

I’ve recently made a few improvements to the code, I think there’s a fair chance one of my fixes resolves whatever might have caused the blank screen you encountered. I’ll post an update soon, I just was hoping to add a few more things first.

I’ll look into how to integrate with other extensions that modify the Edit table, but it will be a while before I do, and I can’t promise success. It’s a whole convoluted bag of worms to go down that road…

Thanks for the speedy reply John. I’ll try out your next version when it’s ready.

Yeah, I figured that integrating with other extensions or subsuming their functionality might be rather convoluted but one can hope. In an ideal world, I’d be able to not only control cloning on a per weblog basis but also the display of categories (ala N. Pitman’s Show Categories)

New Years Cheers!