That’s a strange URL structure you’ve got there – are you sure you’re running WordPress? I’d imagine that would give a 404 if so. If you are on WordPress, could you say what you’ve set in the WordPress address and Site address fields in the General Settings page, which will be at –your site URL–/wp-admin/options-general.php
You can try modifying your query using pre_get_posts filter. function mod_query() { if ($query->is_main_query() && !is_admin() && is_search()) { // test print queried search terms print_r( $query->query_vars[‘s’] ); $search_terms = $query->query_vars[‘s’]; $search_terms = preg_replace(‘/\s+/’, ‘+’, $search_terms); // test print after replacing spaces with + print_r( $query->query_vars[‘s’] ); // if all going well you can change … Read more
Found the necessary setup in WPML: [https://wpml.org/documentation/getting-started-guide/language-setup/directory-default-language/][1] Problem solved.
Your problem seems to be related with a misconfiguration of the temporary directory in PHP which is used for uploads and need to be writable when the sever downloads a WordPress, plugin or theme package. If you can not configure it at PHP level, you can define it also in wp-config.php file: define(‘WP_TEMP_DIR’, ABSPATH . … Read more
Instead of playing with .htaccess file I would recommend using WordPress “Redirection” plugin, it allows for redirection and also logs them.
For the .htaccess-question, Stephen has a nice answer to that here: WordPress will overwrite the entries between ‘# BEGIN WordPress’ and ‘# END WordPress’. While most plugins will create their own begin and end tags and only update within those tags. Simply put your custom entries outside of any custom tags/comments and they SHOULD be … Read more
Typically if your subdomain’s root is the folder with WP installed, then just create a .htaccess file there. That always works for me. Example: public_html -> random etc.. mywpfolder (the wp folder) wp-admin wp-content etc.. .htaccess (create htaccess file here or simply copy/paste the primary one here) EDIT Do you have the other installs in … Read more
In your root .htaccess: RewriteEngine on RewriteRule ^blog/(.*)$ http://www.newdomainyouknow.com/blog/$1 [R=301,L] OR in your subfolder .htaccess RewriteEngine on RewriteRule ^(.*)$ http://www.newdomainyouknow.com/blog/$1 [R=301,L] You can remove all other entries. But this will move all request from one domain to the new domain : for example http://oldandboringdomain.com/blog/cool-staf will be redirected to http://www.newdomainyouknow.com/blog/cool-staf With 301 redirect (permanent) which mean … Read more
finally I completed, using this below hook mod_rewrite_rules function output_htaccess( $rules ) { $new_rules = <<<EOD RewriteEngine On RewriteCond %{SCRIPT_FILENAME} !-d RewriteCond %{SCRIPT_FILENAME} !-f RewriteRule ^(\w+)$ ./index.php?id=$1 EOD; return $new_rules . $rules; } add_filter(‘mod_rewrite_rules’, ‘output_htaccess’);
A rule of thumb when thinking about restricting content on the internet: If your client can see the data, they can have it, this is how the internet fundamentally works. Yes you can make it harder for people to get access to the thing you are attempting to restrict them from, but ultimately as soon … Read more