@Cim
The error log doesn't show anything. However, when using the devloper tools with Chrome, there is a list of errors. For one image from photobucket, it gives the image proxy url with the image url following it, then the token info. In the image url, the colon and slash marks are replaced by character entities %3A and %2F respectively.
The image was shown 2 times in the list with two different error messages, "Failed to load resource: the server responded with a status of 403 ()" and "Failed to load resource: net::ERR_SPDY_PROTOCOL_ERROR"

The other 2 items in this group also had the "Failed to load resource: the server responded with a status of 403 ()" message
One if is video from Facebook and one is an image from facebook. Both also had the character entities instead of the colon and slash mark in the direct link. I used Firefox to get the direct links to both the video and facebook image and then was able to use Chrome to view them.

@ Steve Clay, Thank you for the link. I will do as you suggest.

Just an FYI for those who have an https site and who are using the "Image Proxy" plugin:

If images posted from photobucket don't show for members using Chrome and sometimes for members using IE, Safari and Firefox, there is a work around. Ask your members to add an "s" after the http in the image tag for images stored on photobucket before they post. This includes images for the comment sharing site, Satisfaction.com, whose images are stored on photobucket.

We have not found out why the plugin does not work "as is" with images from photobucket, and may never know, but adding the "s" works for now.

I guess it depends on the SSL and browser. I remember Elgg didn't show any of my images from non-secured links.

set_page_owner($_SESSION['user']->getGUID());

elgg_set_page_owner_guid(elgg_get_logged_in_user_guid());

$current_user = $_SESSION['user']->getGUID();

elgg_get_logged_in_user_guid();

$customstyle_object = $user->getObjects($metadata_name, 1, 0);

$customstyle_object = elgg_get_entities_from_metadata(array(

'metadata_names' => $metadata_name,
'metadata_owner_guid' => elgg_get_logged_in_user_guid(),
'limit' => 1,

));

$customstyle_object = $current_user_entity->getObjects("customstylebackground", 1, 0);

$customstyle_object = elgg_get_entities(array( 'type' => 'object', 'subtupe' => 'customstylebackground', 'owner_guid' => elgg_get_logged_in_user_guid(),'limit' => 1 ));

$customstyle_object = $current_user_entity->getObjects("customstylecolors", 1, 0);

$customstyle_object = elgg_get_entities(array( 'type' => 'object', 'subtupe' => 'customstylecolors', 'owner_guid' => elgg_get_logged_in_user_guid(),'limit' => 1 ));

I've not tested it with this plugin so use it at your own risk.

Thank you! Thank you!

I'll go test it out and let you know what happens.

Thank you for the code. I'm getting a little closer to where I need to be.

I did catch a typo in the last two sets of code you gave me. I'm pretty sure 'subtupe' should be 'subtype' (first line of each set of code).

 I also made some other changes for code that was deprecated according to the code diagnostic plugin. I also updated the menu to the newer style. There is still a few other changes that the code diagnostic plugin suggests but the suggested change causes a white page with no explanation, so I'm leaving those alone for the moment.

At this point, when I click to save changes from either the background or colors editing pages, the changes are not saved and I get an error message: "The action file for customstyle/savecolors was not found" OR "The action file for customstyle/savebackground was not found". So, I'll be back with more questions as soon as I dig a little more.

Thanks again for the code.

JayT