Debian/Apache system
]]>wp-includes/user.php:613
wp_validate_logged_in_cookie()
wp-includes/class-wp-hook.php:292
apply_filters('determine_current_user')
wp-includes/user.php:3256
_wp_get_current_user()
wp-includes/pluggable.php:70
wp_get_current_user()
wp-includes/l10n.php:97
get_user_locale()
wp-includes/l10n.php:140
determine_locale()
wp-includes/l10n.php:1278
_get_path_to_translation_from_lang_dir()
wp-includes/l10n.php:1240
_get_path_to_translation()
wp-includes/l10n.php:1210
_load_textdomain_just_in_time()
wp-includes/l10n.php:1308
get_translations_for_domain()
wp-includes/l10n.php:177
translate()
wp-includes/l10n.php:289
__()
wp-content/plugins/advanced-custom-fields/acf.php:68
ACF->initialize()
wp-content/plugins/advanced-custom-fields/acf.php:649
acf()
wp-content/plugins/advanced-custom-fields/acf.php:655
Is seen with at least 5.7.1 and 5.7.2
Don’t know what to do next.
# BEGIN BuddyPress Docs
RewriteEngine On
RewriteBase /
RewriteRule (.+) ?bp-attachment=$1 [R=302,NC]
# END BuddyPress Docs
It broke my site as it couldn’t find something related to “your plugin” as it put it. I amended the base to state the folder the site is in, as it’s a multi-site installation. Still broke the site. I moved it to the top of all my various other plugin rewrites, and no change so I had to remove it from the .htaccess file. I was editing the main wordpress .htaccess.
I’ve sent a request to my host asking about this.
Secondly, Any chance the plugin might allow for greater privacy choices beyond “group, anyone and logged in user”??? I’m hoping for “my friends” being added in there as well. Would there be anything I could throw into bp_custom.php to add that to the document privacy choices?
]]>I moved my website to Siteground. All is okay exept this error message:
Your BuddyPress Docs attachments directory is publicly accessible. Doc attachments will not be properly protected from direct viewing, even if the parent Docs are non-public.
It looks like you are running Apache. The most likely cause of your problem is that the AllowOverride directive has been disabled, either globally (httpd.conf) or in a VirtualHost definition. Contact your host for assistance.
See this wiki page for more information.
So I went to the wiki and that tells me:
Doc Attachments inherit the privacy levels of the Docs that they are attached to. This works by redirecting the normal WordPress attachment links to a special script that checks for a user’s capability before delivering the file.
BuddyPress Docs attempts to take additional steps to ensure that your Docs cannot be accessed directly by those who might guess the URLs. Depending on your server setup, you may have to take some additional manual steps to ensure 100% attachment privacy.
Apache
On Apache installations, BuddyPress Docs attempts to protect attachments on a doc-by-doc basis. This means that attachments to private Docs will be served through BuddyPress – ensuring proper authorization – while attachments to public Docs will be served directly by Apache – ensuring the lowest possible overhead.In order for BuddyPress Docs to protect attachments in this way, AllowOverride must allow for subdirectory-specific rewrites. The vast majority of WP installations will have this setting enabled by default. Contact your host for details. For more information, see Apache’s documentation for AllowOverride.
But to be honest, i dont have a clue what to do ?
So i have asked my hoster, but they say then cannot give me an advice about htaccess rules. And said i have to ask the buddypress docs people.
Can someone please explain to me what Rule i have to use?
On siteground they say this about allowoverride : The AllowOverride directive in the Apache’s configuration has been set to ‘All’ on all servers.
Any help is really appreciated.
Warm regards
Jap
]]>AllowOverride All
in the config files. When I would enable this, I could no longer save changes in the Permalinks settings page (https://www.mydomain.com/wp-admin/options-permalink.php). Whenever I would make a selection (i.e. Post Name) and click save, it would revert back to the setting when I opened the Permalinks Settings Page.
After trying a couple of different things I realized if I would change the permalink setting then set AllowOverride All
the redirect would work properly. However when I would close my browser, I would be logged out and unable to log back in. On entering my login info and clicking log in, it would loop me back to the login page prompting me to enter my credentials again.
I’ve tried disabling all plugins, clearing my browser cache, changing the AllowOverride
in my default configs as well as my site specific configs.
Running on: PHP 7.3.13, Ubuntu Server 18.04.3 LTS, Apache 2.4.29, MySQL 5.7.28
]]>When trying to install Ninja Firewall Full WAF Sith Litespeed I have an error 500 directly and I need to delete htaccess and deactivate the plugin from FTP to have my website back…
Any documentation to resolve this problem ?
Thanks
Samuel
Upon attempting to “activate recommended features” I got this error message:
“recommended features failed to activate. Api404error”
There is another post with the same error:
https://www.ads-software.com/support/topic/recommended-features-failed-to-activate-api404error/
I posted a lot of my system setup there, and was asked to create a new post here.
Any help would be appreciated. Thanks in advance.
]]>I had error 403 when I tried to access to dashboards of new sites in WordPress 4.4.2 multisite installed in XAMPP v3.2.2 localhost (Apache/2.4.18 OpenSSL/1.0.2e PHP/7.0.4). And the new site is displayed without an assigned theme.
After verifying that in PHP info of my localhost I have the mod_rewrite in Loaded Modules and to enabled the AllowOverride All directive in the DocumentRoot (changing None for All in httpd.conf of Apache), errors are not solved.
However, I have found that removing the path C:/xampp/htdocs/wordpress/ in code fragment below show (WordPress generates this code for .htaccess) I solve the problem, or at least partially solved:
...
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) C:/xampp/htdocs/wordpress/$2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ C:/xampp/htdocs/wordpress/$2 [L]
RewriteRule . index.php [L]
So, I manage to solve two errors: I can access to dashboard of the new site and display an assigned theme. However, I wonder if the changes made may adversely affect other “parts”.
I would like to have your ideas or suggestions about this topic.
Thanks
]]>define('WP_ALLOW_MULTISITE', true );
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
define('DOMAIN_CURRENT_SITE', 'three.ninjaforms.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);
.htaccess:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
Rewrite is enabled in Apache and AllowOverride is set in every fricking place I can find, yet I still get “File Not Found” when trying to access any menu in the dashboard of a network site (any page with admin.php)
]]>I have a new installation of WordPress 4.1 on OpenSUSE 13.2. I have only the default blog setup with (1) sample post I created.
I want to be upfront that I’m not a Linux Expert, but a novice.
When trying to enable the PERMALINK to use POSTNAME, my base website shows up fine. But when I click on the categories or post or comment, it throws a 404 error.
I can log in and access the WP-Admin with NO errors. I read other posts about switching back to the DEFAULT for permalink, saving, then going back in and changing it back to POSTNAME. When I do that, it still fails when using permalink = POSTNAME
I was reading about how to trouble shoot this further. My Apache configuration file /etc/default-server.conf has this in it:
<Directory “/srv/www/htdocs”>
Options Indexes MultiViews
AllowOverride None
Require all granted
</Directory>
Some articles suggested that I needed to have .htaccess files and that WordPress would create that file automatically. However, in my directory /srv/www/wordpress/ has no .htaccess file
I created one manually with this in it:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
I manually created that file. I used CHMOD 755 .htaccess on ths file.
If in the default-server.conf I change Allow override all instead of none, I get an error that shows I’m forbidden from viewing the file.
I just wanted to be open and truthful about what I have tried. I enabled mod_rewrite my modifying the default-server.conf to load it. PHP_INFO() shows it’s loaded.
When I originally installed OpenSUSE it was 13.1 about four days ago. THen, there was an update notification to update to 13.2, which I did and rebooted.
I am not sure if this is what broke the ability to use POST NAME option of the permalink in wordpress. But any other option other than DEFAULT does not work.
I also have removed all plugins. I was using Yoast SEO Plugin and a widgets sidebar plugin. I have removed them all.
I have installed phpMyAdmin and webmin. Webmin is showing that I have Apache 2.4.10 installed. phpMyAdmin and Webmin are running OK as long as I have Allow override none enabled.
So what I think is that there’s something wrong with how I’m trying to enable .htaccess files to be allowed. if I enable AllowOverride All in the default-server.conf all access is forbidden.
I think that is the root issue, but I do not know what to do to fix this issue.
It is my udnerstanding that if mod_rewrite is loaded and AllowOverride All is in the default-server.conf that WordPress will create and manage the .htaccess file.
I just don’t know what else to do. If I enable AllowOverride All everything is forbidden.
I would be very grateful for any assistance please. I tried being detail oriented, reading a lot to try to solve this myself. But I’m not able to get the PERMALINK to POST NAME to work, and I think it’s because the installation and configuration of Apache to allow .htaccess is not ok, or some how the permissions are not right when AllowOverride All is on.
Thank you.
]]>