macaou

Hi Pascal, it’s because we use Buddypress (which is a social networking plugin) and the 1st problem is that the author of the web stories can be seen (which you can circumvent in a bad way with css or in a good way via php). The 2nd Problem is that we want to create some stories that should only be seen by logged in users (sometimes we use generated content of those users in our stories – at least that’s the plan) and some publicly for search engines & the public. The 3rd Problem is that there is no way to change the layout of the automatically generated page (without adding or changing the source code or css), so it currently just looks bad due to the different sizes that we have used for the cover images (we can of course use the same dimensions for all pictures but it just makes things more of a hassle).

Would you be more likely to keep the page around if you had more control over itt to improve styling or add custom content?

Yes, if the mentioned Problems could be solved by having more control.

The github feature request is about different roles being able to edit web stories however i want to restrict the automatically generated site example.com/web-stories to only being seen by the admin or just 600.

• This reply was modified 4 years ago by macaou.

can you put @ini_set(‘session.cookie_httponly’, true);
@ini_set(‘session.cookie_secure’, true);
@ini_set(‘session.use_only_cookies’, true); inside your wp-config and use buddyboss platform instead (They had a huge security hole with the messages that they fixed today which might cause the issue right now).

• This reply was modified 4 years ago by macaou.

WP Debug is disabled
PHP Version 7.4
WP Version 5.5.3

The huge security hole was fixed and was caused by the buddyboss platform. You can mark it as solved

It was a security http header Set-Cookie which was causing the issue. Probably because of a duplicate entry one time inside the htaccess and one time inside the wp-config.

• This reply was modified 4 years ago by macaou.
• This reply was modified 4 years ago by macaou.

i figured it out it was a security http header Header
that caused the issue.

• This reply was modified 4 years ago by macaou.

Console Error:

Uncaught TypeError: a(...).superfish is not a function
    desktopMenuToggle https://example.com/xxx/assets/js/custom.min.js?ver=3.2.0:1
    <anonymous> https://example.com/xxx/buddyx/assets/js/custom.min.js?ver=3.2.0:1
    jQuery 3
    <anonymous> https://example.com/xxx/buddyx/assets/js/custom.min.js.js?ver=3.2.0:1
    <anonymous> https://example.com/xxx/buddyx/assets/js/custom.min.js.js?ver=3.2.0:1

• This reply was modified 4 years ago by macaou.

It seems Buddyx is the causing the issue. You can mark it as solved thx.

sorry it’s display: none;

My initial plan was to restrict access to the page /web-stories that is automatically generated by the plugin entirely so that non other than the admin have access to it. So my answer is yes, i wanted to create different access levels but i already solved the problem in my own way so you can mark this as solved. Although It would be better if we were able to customize or disable the automatically generated site without changing the php files.

• This reply was modified 4 years ago by macaou.
• This reply was modified 4 years ago by macaou.
• This reply was modified 4 years ago by macaou.

Simple CSS Solution

.rssiconexample {

display: hide;

}

The rssexample has to be of course replaced with the real ID/Class.
The other method would be to remove the function via php.

I tested it today with only Buddypress, BBpress and BSR activated + the twenty twenty theme and the problem is still there. I checked the console and the only Warnings (No Errors) that i received is:

Cookie “bp-message-type” has been rejected because it is already expired.
Unknown property ‘speak’. Declaration dropped. dashicons.min.css:2:42822
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. dashicons.min.css:2:42950
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. admin-bar.min.css:2:429
Unknown property ‘speak’. Declaration dropped. admin-bar.min.css:2:4126
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. admin-bar.min.css:2:4204
Unknown property ‘speak’. Declaration dropped. admin-bar.min.css:2:6300
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. admin-bar.min.css:2:6364
Unknown property ‘speak’. Declaration dropped. admin-bar.min.css:2:9675
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. admin-bar.min.css:2:9739
Unknown property ‘speak’. Declaration dropped. admin-bar.min.css:2:11165
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. admin-bar.min.css:2:11229
Unknown property ‘speak’. Declaration dropped. admin-bar.min.css:2:15714
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. admin-bar.min.css:2:15815
Error in parsing value for ‘min-width’. Declaration dropped. admin-bar.min.css:2:17735
Error in parsing value for ‘min-width’. Declaration dropped. admin-bar.min.css:2:17765
Error in parsing value for ‘width’. Declaration dropped. style.min.css:11:2262
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:18659
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:51193
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:51301
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:51772
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:51852
Unknown pseudo-class or pseudo-element ‘-ms-expand’. Ruleset ignored due to bad selector. buddypress.min.css:1:63853
Error in parsing value for ‘-webkit-appearance’. Declaration dropped. buddypress.min.css:1:68533
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:88351
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:88607
Unknown property ‘-moz-flex’. Declaration dropped. buddypress.min.css:1:89720
Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. style.css:813:7
Error in parsing value for ‘overflow’. Declaration dropped. style.css:1331:12
Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. style.css:2177:29
Ruleset ignored due to bad selector. style.css:2815:47
Ruleset ignored due to bad selector. style.css:5389:49
Ruleset ignored due to bad selector. style.css:6044:49
Ruleset ignored due to bad selector. print.css:131:10
Unknown pseudo-class or pseudo-element ‘local-link’. Ruleset ignored due to bad selector. print.css:139:10
Error in parsing value for ‘-webkit-box-pack’. Declaration dropped.

Hi,

rtmedia has it’s own folder so i wrote a simple script and put it into the folder which only allows users who are logged into the site to view media items. If a user would for example share example.com/upload/rtmedia/picture.jpg a logged out user won’t be able to view it and will be redirected to the login page.

The Problem with the Flexi approach is that i can’t just write a simple script for it because i would also make the normal wordpress pictures not viewable for logged out users. If you share a picture uploaded via Flexi with a logged out User he can still see that picture.

• This reply was modified 4 years, 2 months ago by macaou.
• This reply was modified 4 years, 2 months ago by macaou.
• This reply was modified 4 years, 2 months ago by macaou.
• This reply was modified 4 years, 2 months ago by macaou.
• This reply was modified 4 years, 2 months ago by macaou.

Sorry i didn’t have time to test it on a staging site yet. I’ll do it soon.
I think the problem is caused by either youzer my theme or my code mods that i’ve done so it might take a while.