Re: NOT ABLE TO POST A AVATAR ?

Posted by GregChapman on Mar 18, 2012; 9:02am
URL: https://support.nabble.com/NOT-ABLE-TO-POST-A-AVATAR-tp7379795p7383152.html

Hi Claude,

I can't account for your problem, but I can confirm that what I describe below is the way Nabble has worked for me for as long as I can remember and has not changed within the last couple of weeks...

Whether you click on your name or avatar in the following locations you get to the "User Posts" page as indicated by the URL seen on your browser's status line while you hover over the link.







In the first two cases it doesn't matter whether you hover/click on the name or avatar, the link takes you to the same place:
http://loa-computer-help-plus.2634207.n2.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=115314

You will also get to that page by choosing the "My Posts" option from the menu under your username at the top right of any Nabble screen.

On the User Posts page above the list of posts there appear a number of links. These vary depending on whether you are looking at the posts...

1. of another user and are not logged in
2. of another user and are logged in
3. of your own posts and are not logged in
4. of your own posts are are logged in

In Case 2 the available options will vary according to your permissions, e.g. depending on whether you are an "Administrator" , "Member", "Registered" or "Anyone".

Only in Case 4 will the links include one to send you to the "Account Settings" screen. You have also always been able to get to the "Account Settings" screen from the menu under your username at the top right of any Nabble Screen. (Obviously, that requires that you are logged in.)

As for the inserting images issue, I can only refer you to Hugo's last post in this topic:
http://nabble-support.1.n2.nabble.com/Inserting-a-picture-in-my-Nabble-Web-Page-tp7309990p7309990.html

It may be that both these issues are browser related, but the inability to set an avatar does appear to be related to whether Nabble recognises that you are logged in and that could be cookie related. Hugo is better placed to address that problem.