• i have setup a multisite blog. i installed the plugin. everything seems working until after cropping the avatar. it seems like the final step can’t get the image through the url: wp-content/plugins/user-avatar/user-avatar-pic.php?id=3&w=150&radom=1301958908. has anyone had the same problem? help please….

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor Enej Bajgori?

    (@enej)

    hey mlcy44

    I developed the plugin to work with multi site setup. You will need to provide me with more info. About your set up. Like what happends when you got the url of the image
    what error do you get?

    Cheers Enej

    Plugin Contributor Enej Bajgori?

    (@enej)

    Thread Starter mlcy44

    (@mlcy44)

    when i view the url of the image, it gave me a blank page.

    Plugin Contributor Enej Bajgori?

    (@enej)

    What kind of permissions to you have set on wp-content/uploads/avatars/
    folder

    Thread Starter mlcy44

    (@mlcy44)

    i think i found the problem, but not yet a way to fix it. i saw the warning of about the timezone isn’t set. in wp, it sets to UTC. somehow when the page calls this function, show_cache_file(), because of the timezone warning, it didn’t render the image out, even the file is there.

    Plugin Contributor Enej Bajgori?

    (@enej)

    Hi mlcy44
    I am glad you solved the problem,
    Thanks for posting it here. I will see if there is something I can do about that.

    Enej

    I’ve had a similar issue here, which I resolved by removing the ?radom parameter from the API call in the function user_avatar_fetch_avatar in user-avatar.php, so the output url moves from this:

    https://example.com/wp-content/plugins/user-avatar/user-avatar-pic.php?id=1&w=150&radom=1303064666

    To this:

    https://example.com/wp-content/plugins/user-avatar/user-avatar-pic.php?id=1&w=150

    What does radom refer to here in this plugin ?

    I don’t see any references to it anywhere else in the code, and I had no luck googling for the phrase either.

    Hmm.. removing this line shows the image, but I’m now unable see the a new version of the cropped image in the back end admin after doing this.

    I’m able to see the new photo in the file system, and hitting the url directly shows the updated photo, but when displayed in the WP admin interface and the actual crop screen, the old image is still persisting.

    I’m assuming the radom part of the url was referring to some kind of caching before, but I don’t know enough about caching and php to go any further than this.

    Any ideas on where to look to work out how to debug this?

    I get this behavior when WP-cache switched on and with it off, and I’m using WordPress 3.1.1 and php 5.3.4 on OS X for development.

    Thanks the plugin otherwise – apart from this wrinkle, it’s a lovely piece of work ??

    Plugin Contributor Enej Bajgori?

    (@enej)

    Hi chris_d_adams

    > What does radom refer to here in this plugin ?
    What random does is it create a unique url for the image. This way browsers are able to cache the image and not having to fietch it each time from the server. It’s value changes every-time you upload the image because it uses the images file generation time to create a random string.

    What I think might be happening is:
    The browser is caching the old image. Your server might be set to to have images served using headers that have an tell the browser to cache the images for a long time. (Which is a good practice.)

    I think keeping the random part is a good idea. (Which by the day is a spelling mistake )

    The new image should appear right away when you click close on the overlay. If it doesn’t then there is a javascript bug.

    If it doesn’t appear when you refresh your browser. Then there might be a some sort of configuration issue. What do you get when you try to go to the file?

    I would like to call this plugin on a page how would i do that?

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘[Plugin: User Avatar] can't get avatar on multisite blogs’ is closed to new replies.