Can't .get() key as a non-admin

[Wormopolis]

Jul 11, 2013 15:22:38 GMT -8 Tim Camara said:

I don't believe so, but I'm pretty sure it's mostly a straightforward implementation of api.jqueryui.com/dialog/.  I dug up a quick example:

proboards.dialog('dialog_id', {
html : "Dialog Content",
title : "Dialog Title",
height : 700,
width : 700,
resizable : false,
buttons : [{
        text: button,
        click: function() {}
         }]          
});

I wish I could bookmark a single post...

[Bennett 🚀]

I figured things out, thanks though.

I'm just having IDs spit out in posts so people know money is being taken/given. I also am avoiding dialogs because I want things to be super simple to complete, thus the reason for UBBC.

[Wormopolis]

you might consider having it just tag the recipient in the post. the recipient goes to the post to see why they were tagged and they see a button that they press to confirm the transaction. this way, you store the initial data in the post, then upon clicking the confirm button, the money is added to the recipient and data removed/changed in the post key

[Wormopolis]

hey Tim Camara , along these lines, since you cant SEE a super user key unless they are on the page, but you can WRITE to it, is there a way to append to what might be in there without destroying/overwriting its current data?

[Tim Camara]

Currently there isn't.

[Wormopolis]

Jul 11, 2013 11:19:00 GMT -8 Tim Camara said:

It is global in that any user (with the proper permissions) can get/set a super key. However, we don't load all the values for a particular super key on every page load. Instead, we load the values for those users whose data is loaded for the page currently being viewed. This drastically cuts down the amount of data we could theoretically need to load on every page view when a super key is in use. I don't know much of anything about your specific plugin, but the general idea is to assign the data relevant to a particular user to a key that corresponds to that user. So, from your example, the key data that is returned with .get(1) would be the data describing the admin user, while the key data returned with .get(16) would refer to the data describing 'shadowlark2'.

I had a thought about this.  what if the get function first checked the data loaded on the page (for users already on the page), and if not listed, THEN maybe it could do an ajax request for the data and store it in a windows.variable.  later .get() calls would check the page, then the variable, THEN an ajax request.

or does that just open the doors to massive ajax flooding?

[Tim Camara]

If you're just looking for a way to append to a key, the latest update that I'm currently working on will solve that problem. Aside from that, generally speaking, I can't think of a situation where you'd want to affect the data of a user that isn't loaded on the page anywhere.

[Wormopolis]

oh there have been many. notification systems. money transferring. anything that involves some sort of transaction/interaction between 2 members has the potential.

but if you already have "push" and "pop" in the works, then that might have to be the solution.