This question is related to the 'Avatars don't show in Admin' thread created recently (https://xoops.org/modules/newbb/viewtopic.php?start=0&topic_id=72652&viewmode=flat&order=ASC&type=&mode=0), but different as I explain below.

As other threads I've started in the last 24 hours will tell you, I've updagred from 2.4.4 to 2.5.3. and I have added the Profile module to enable CAPTCHA facilities.

However, the avatars are all missing now and users do not have the option to upload one themselves, despite the option being set to 'yes' for "Allow custom avatar upload?" Preferences --> User Info Settings.

In Preferences --> System Module Settings, I also have 'Active Avatars' set to 'Yes'.

Despite that, all new users get a silouetted figure as a default Avatar, and if you click on 'Edit Account' there is no button to add or edit Avatars as there used to be.

If I go to Avatars Manager, the it recognises the 66 System Avatars plus a few dozen custom avatars in terms of numbers, but when I click on them to see a gallery of pictures, all I get is the names of each avatar with no actual picture - i.e. a thuimbnails gallery with no thumbnails.

The image path is
"Choose files in: C:\path\to\my\website\lost-doggies.com/uploads/avatars/"

As far as I know, the \ and / slash issue should be resolved by the PHP functions. Yes - the site is hosted on Windows Server 2008 and IIS.

If I then explore ImageManager itself, again, it sees that I have many categories and hundreds of images, but it cannot show any of them. This might help explain why my WF-Channel pages are not working either, as they too contain images? (https://xoops.org/modules/newbb/viewtopic.php?topic_id=74296&post_id=341579#forumpost341579).

I'm not sure if it's related, but I detected a problem similar to this using another CMS and it was due to the imagemanager directory being moved. It was fixed in that (http://community.?????.org/modules/newbb/viewtopic.php?topic_id=4426&forum=49&post_id=39570#forumpost39570). I'm not sure if that problem has been replicated in some way here?

Thanks

Ted
(PS - this is why I hate upgrading....4 threads in and about 6 hours in and I'm still ironing out problems).

FIXED!

Turned out it was because I was using the Profile 1.62 version, instead of the seemingly much more recent 1.70 version.

Having eventually scratched round the numerous outdated and invalid download links, I eventually found 1.70 at http://www.chronolabs.coop/binaries/, specifically, http://bin.chronolabs.coop/xoops2.5_profile_1.70.zip. Having updated my Profile module with that, my avatars are all accessible and if my users clieck 'Edit Account', the avatar button now exists! Happy days.

Come on guys - if this Profile module is so central to the entire Xoops system these days, why on earth is it not maintained as part of it, or at least packaged with it. It's caused me hours of pain!

I have taken the liberty of adding the latest download link to the outdated news entry, here https://xoops.org/modules/repository/singlefile.php?cid=101&lid=1949&com_id=54180&com_rootid=54180&com_mode=flat&com_order=0#comment54180

Ted

Supported profile version is the one delivered with the core, and it works just fine.

No way that updating to profile 1.70 would solve the above problems, specially the one related with image manager(not at all profile related).

You probably missed some step on the upgrade process. Maybe you forgot to run the upgrade or to update your modules. What else have you done before installing profile 1.70?

By the way, Core profile version is 1.61. I recommend you to use it instead of 1,62/1.70

I wonder if it was due to missing a System module update after updating or reconfiguring one of the other modules. I updated the WF-Resources module as part of another problem, but didn't run the System Module update I don't think, so maybe it's all caught up with itself.

I didn't realise Profile was packaged with the core because it didn't present itself as one of the available modules and my site continued to use the default and older registration page system until I added this module. It all started because I needed a CAPTHCA process for my registration. After upgrading the core Xoops system, no CAPTCHA appeared until I installed Profile module that I linked to above.

So many bits and pieces so as you say, probably one step was missing somewhere amidst the process.

Yes, but remember, the core profile module uses captcha plugins that are in core and it is tested by core developers in each release. You can also recaptcha or other captchas provided by core or Framework. This captchas will also work in other modules, like contact modules. The profile module delivered by wishcraft uses its own version of captcha and make use of functions that will be deprecated on future versions of XOOPS. I strongly advise you to stay away from profile modules release by third parties.