Just for your information, We did implement this in 3.2.15 last time but we noticed that once we switch to this behavior "ViewAs" page by default, it will cause a lot of issues because the first we implement this "Page" feature all the thing is actually based on NOT to show "ViewAs" page at first, so it is not an easy task to change this behavior and we decided to change back this behavior to original in 3.2.16.

Okay Arlex.
And if I modify the following file, what problems will I have ?
Because yet it seems to work well.

/administrator/components/com_easysocial/includes/template/helpers/form.php

		$viewAs = $session->get('easysocial.viewas', 'user', SOCIAL_SESSION_NAMESPACE);

Replace with :

		$viewAs = $session->get('easysocial.viewas', 'page', SOCIAL_SESSION_NAMESPACE);

Thank you,
Philippe

If I recall correctly, these are the issue what we encounter last time :

1. Site admin can't react to any stream item from the Page (Don't test it from his own Page).

2. if using Site admin react one of the stream items from the Page, it will show duplicate data from the reacted list.

3. the reaction part show duplicated e.g. react "happy" then react "sad", it will mart these reaction +1 from this single user.

4. When the Page admin react the stream item e.g.
- Open 2 browsers and log in Page owner and Page admin.
- Page owner submit a new story post.
- Page owner react Love.
- Page admin react Happy, it will show the correct even refresh the page.
Okay, the issue will happen now, when the Page admin react Love (viewas page)

the expected result should be love = 2 but it showing happy = 1 and love = 2
but when you refresh the page, it will show correctly.

5. and etc.

Thank you Arlex for your your detailed explanations

This also poses a problem on the Native Mobile App.
Because if I own a Page, I cannot post as a Page on my Page.

Logically here, the correct behavior should be to publish as a Page.

Philippe

This also poses a problem on the Native Mobile App.
Because if I own a Page, I cannot post as a Page on my Page.

Logically here, the correct behavior should be to publish as a Page.

I see, thanks for the report, I will log into our issue tracker in native mobile milestone so that it will show an option "ViewAs" that allow the owner to select.

But in Native App too, please make sure that View As Page is selected by default.

Because otherwise the owners of the Pages won't pay attention.
And they will post as User instead of as Page

The easiest would probably be not to offer a selector, and that an owner or an admin of a Page can only publish as a Page. This is the main purpose of a Page.

Thank you for your understanding,
Philippe

It is not possible to set the ViewAs default to Page, but we will see what we can do about this in native mobile.