Hi,
At my homepage, I can only see public posts. I cannot see my private posts.
I re-created a menu>>private, I am still not able to see private posts.
Please advise.
Hi,
Blocks and grids will only display published public posts. These elements need public posts to display for any instance. Please correct me if I misunderstand.
Thanks
Sorry, I am confused here. If I have a category that made up of private and public posts. The default wordpress would allow me to view those private and public posts if I were to sign in as administrator.
But when I use Newspaper theme, despite sign in as administrator, I can only view the public posts?
Further, I noted if I install user access manager plugins or other similar plugins, to assign category or page in the menu bar as private, it has absolutely no effect on the frontend, ie. a visitor would able to view the category/page displayed at the menu bar!
Please advise.
Hi,
The blocks and grids will not display private posts, that is the way the theme is designed.
Regarding user roles, the theme uses the default user role capabilities
– https://codex.wordpress.org/Roles_and_Capabilities
Those could only be changed with plugins that have maybe the options needed. There are no theme options by default in this matter.
Thanks
Hi Simion,
My understanding is for WordPress – if one login as a super user, it can view anything at the homepage, etc. Everything is transparent to super user. But I am not experiencing this happening.
For clarity, I have sites created to validate those claims. Further, I have used other themes that display exactly as my claim is – that is, if you are a visitor, yes then, you are only visible to the public posts. But if you are a super user, you should have the rights to see all posts type, unless the default WordPress routing is changed.
Hi Simion,
I visit the WordPress.org, confirmed my understanding is correct – you need to fix the routing! From WordPress.org:
Private content is published only for your eyes, or the eyes of only those with authorization permission levels to see private content. Normal users and visitors will not be aware of private content. It will not appear in the article lists. If a visitor were to guess the URL for your private post, they would still not be able to see your content. You will only see the private content when you are logged into your WordPress blog.
Once you change the visibility to private, the post or page status changes to “Privately Published” as shown. Private posts are automatically published but not visible to anyone but those with the appropriate permission levels (Editor or Administrator).
Hi,
Please edit this file from the theme, and the private posts will be displayed
– https://www.screencast.com/t/XP5vHNAv
Comment or remove the line of code like this
– https://www.screencast.com/t/QrN99wsEMG9S
Thanks
Thank you!
One question – for the future update of the theme, would the issue be fixed? Or the suggested solution is meant only to fix to this request?
Cheers!
Hello,
I have passed this information on to our development team and it is very possible we will implement it in coming updates but I cannot promise anything though.
Thank you!
Hi Bogdan,
I believe all themes built should comply to the basic WordPress structure. As such, I see this as a bug to be fixed. I bought this with the understanding that it comply to the WordPress structure, at least the basic. The theme should not change the fundamental way a post is displayed.
Further, as I look at Simion screenshot, it appeared to me that both are the same image!
Please advise.
Hi Chris,
Thanks for the clarification. I had tried and it seemed to be working.
Questions:
1 Would the future release fix the issue? If it is that easy to fix, why it can’t be assured to be fixed in the next release?
2 If the future release does not fix the issue – is this the way to fix it?
In short, I need a permanent solution, not a temporary solution and need to be aware of the implication of that solution given to me.
The point I wish to highlight – the theme should not change the basic structure of how WordPress function. If it does not comply as the customer, we should have the right to ask for a refund.
Hello,
1) We pick very carefully what we implement into our themes. There are multiple implication to even the slightest change which have to be decided by the development team. Usually any at all request no matter how small must become more popular before we decide to implement it into the final product.
2)You do have the right to ask for a refund. Please request one here if you need one and we will provide it: https://themeforest.net/refund_requests/new
Thank you!
To be fair, it took me sometimes to make that decision to buy the theme. To me, the theme is closed to perfect, except the issue raised.
Further, I can see the hard work put in to build the theme into perfection. Hence, before I ask for a refund, to be fair to you and to me, I need to know if the issue raised, is to be fixed. From my perspective, I do not consider that as “new” feature because that is how WordPress supposed to behave – so it is a “bug” to be fixed, regardless of popularity of the “feature”.
Of course, if the company believes that that “bug” is trivia and would have no intention of fixing it, then, I would have to access from my end the implication of that whether I can accept it. If I cannot, then I would proceed to ask for a refund.
Thanks.
or,try the fix 😉
if only 2-3 people out of 10,000 people ask about that, not big on the to do list.
All themes with page builders and complex options, built-in features ala plugins, may ‘change the way wordpress works’ — as WP doesn’t do a lot of things out of the box.
(Only my opinion, I do *not* work here!)
Chris,
Complexity should not be an excuse in not complying to the core of how WordPress function. I have seen theme with similar complexity as the Newspaper, however, they are still able to comply with WordPress’s core.
It is difficult, but it does not mean you can break the “rule”.
In this case, I just happened to notice that “non-comply” bug…if the developer does not comply to WordPress’ core, how do we know which part of the theme it developed comply and which part does not?
For any meaningful troubleshooting, should that be one, we first have to iron out that all theme and plugins are comply to the basic core of WordPress. Then only we could identify which plugins caused the issues. If we could not assure of that core is met by the all themes and plugins, we would face nightmare should there be problems!
Put it simple, I like the theme and I just want to know the company’s stand – whether it would address it or otherwise. If the answer is “no”, then I would re-access the important of that “bug” to me, if it is unacceptable to me, I will seek for a refund.
I want a clear reply from the company on its stand. Appreciate your understanding.
Thanks.
Hello,
The option will not be implemented in the final theme.
The WP implementation was changed by our developers due to the block sorting options available for our theme elements. As you can imagine, every piece of code and every functionality that does or does not work has a purpose. The decision to remove the private posts from our theme modules and blocks has been made to maintain the proper functionality of our block elements and sorting options.
Thank you for your understanding.
Bogdan,
Ok, I understand where you are coming from.
May I clarify if the solution given to me by Simion is a fix? In other words, for future release, can I use the same method to fix it?
The reason I am asking this is, I might not need the full complexity of the theme. In this case, can I just deploy the given solution as a fix?
Your clarifications please.
Thanks.
Yes, in future versions you will still be able to use the exact same solution as provided above. Use the solution provided by Simion.
Thanks
One more question, what would I trade-off is I were to use Simion’s solution?
To be precise, if Simion’s solution is deployed what are the “blocks” or “elements” that I cannot deploy?
Please clarify.
Thanks.
Hello,
Our main concerns regarding this issue is your block filtering. If you filter your blocks to show specific content and that content has privately published posts, your users content will be different than the one you see and plan. We do not know of a bug or part of the theme that will break using this implementation. We only just want to avoid confusion regarding these posts and our blocks as much as possible.
Thank you!
Bogdan,
Here is my understanding, correct me if I am wrong:
”
Let’s say, I have a category called News. Within the category, it contains public posts and private posts.
When I use the block’s filter to show the News:
Administrator – will see both public or private posts
Public – will see only public posts.
”
If the understanding is right, from my perspective, administrator should be aware of the different right, if the administrator set the post to private – “it is not meant to be seen by the public”, isn’t it? Please clarify.
My concern is it might have other unknown consequence which I have to further try out.
Thanks.
No, there will be no other consequences besides the ones you mention as far as we know.
But we have not tested the block filters as this functionality has always been missing from our theme and we have developed the post filters much over time and since we have not tested the filters, it is hard for me to make a prediction to what till break or not. Test it out and try the post sort orders: https://www.screencast.com/t/v9gYQPr7lQO
I can provide no more information on this as it is simply not tested. We have provided a solution to your problem but in order for us to discover ALL of the implications it will mean rigorous testing and we cannot offer such services at the moment. We do not have a customization department.
Thank you for your understanding.
Bogdan,
I understand and thank you. I have did some tests – I derive the conclusion the solution given is not able to address all the concerns that I have – especially the compatibility issues with other plugins that comply to WordPress’s standard on private posts and I need to use those.
Based on the above, I would seek for a refund.
Thank you.
