orangeworx

Well that’s where I started but the htaccess file in the other subdirectory installations are similarly written…
there would be no reason why the other installs would work but not this one…
I have a feeling it’s something with the main install “thinking” the subdirectory URL is its own… not sure if this makes much sense
example to try to describe it
domain.com/wp-admin >>> admin page of root install
domain.com/install1/wp-admin >>> page not found through root install
domain.com/install2/wp-admin >>> loads admin of install2

@kjodle no it’s not a multisite setup
it’s a main install with other installs in subdirectories…

It’s funny how some people think there’s a quick fix for everything, even so for web security!
I’ve been reading/learning on the matter for months/years and I’ll be reading/learning and applying stuff forever because that’s the truth of the matter, as long as the internet’s here, security will be as well… Once you’re involved in security, there’s no end, it’s a 24/7 job on its own. There will be updates, there will be security issues, there will be patches and the list goes on.

The golden rule here is if you don’t/can’t take the time and effort, have a knowledgeable person take care of this for you.
my 2 cents

Hey there
I have the same issue and it’s not something I can recreate as in some files will edit and save fine whereas others won’t. Sometimes within the same folder…
I’m not sure how having to download/edit/reupload is a solution… What explains this behavior? Why some files and not others?

thanks!

I’ve been having the same issue with OP and several other posters. I’ve already spent a great deal of time trying to figure out wtf is going on here and have yet to find anything that explains this behavior…
I had first started with a 2017 child theme, gone through the “standard” setup, permalinks, static front page etc but I’m not even trying to make a onepage style site with sections … I’m merely wanting to use the one column functionality in “Theme options” which disappeared despite the static front page setting.
So I’ve disabled all plugins that I had, issue didn’t resolve itself, tried to reactivate them one after the other, nothing changed. Did a WP reset and removed my child theme (which really had nothing in it, just the basic style.css) and set my static front page (sample page) and I opened the customizer… what happened then was interesting to say the least… customizer menu loads and a couple of seconds later, “Theme options” appears but that’s about it. Customizer loads as if I had already made changes to the site, I don’t have the greyed out saved button, it’s save & publish and it does not do anything…. whether I make changes or not it won’t save anything.
I’ve gone through another set of resets…. nothing.

I’m planning to do complete wipe and reintall to see if the issue persists…
It’s the first time I notice that so I’m not sure if it was always like so

Ok that’s pretty awesome! So in theory I can have a one-time popup as a language selector with a checkbox to remember preference? would that be difficult to implement? not that familiar with cookie control through a form or if doable either.

edit: btw thanks a lot, I really appreciate the support!

• This reply was modified 7 years, 12 months ago by orangeworx.

@chrystl: thank for responding. Unfortunately it’s not quite what I’m inquiring about. In fact, this option is already activated on my setup. The issue with this is that many users have English OS’s but are primarily other language speakers. In my case, I’m only dealing with 2 language, English and French. I want the option for my site visitors to select their preferred language on first site visit and that selection is saved for subsequent visits (I believe that’s achieved with cookies, not certain on implementation)

I hope this explains things a bit better

Thanks

Hey there and thanks for responding. I think I didn’t explain myself properly. I said user but I should have said visitor. I don’t plan on having registration open for my site so the usermeta db table wouldn’t be accessed for site visitors. I would just like to save the language choice so that when the visitor returns, the site would load previous selection. I wonder if this is only done by cookies.

Thanks

Hey there everyone,
I got to this thread because I’ve been having some issues with the links menu. I’m pretty sure I’ve set this up correctly, it doesn’t require a PhD in quantum mechanics. Create menu (Media Sociaux in my case, the language isn’t the issue because I’ve tried creating and English named one as well) assign menu to social menu location, create custom links and bam! unfortunately no bam in my case… the links/icons are not displaying.
I am using a child theme and my footer text has been modified (by plugin) which could be an issue… other than that I don’t have other ideas.

Thanks for reading!

Hello Takayuki and thanks for your answer. I had some issues with this as some translations were not “sticking”, weird…. I went through both languages one after the other and then the translations had been saved.

thanks again

• This reply was modified 8 years, 1 month ago by orangeworx.

@adnansaleem: Of course, you create your cashier users with limited access roles and you decide which pages they have access to, just like the demo.

HTH

so after a few days of trying different on/off combinations of plugins, I’ve arrived at the conclusion that there’s some kind of problem and query monitor just confirmed it.

Strict (Suppressed)	call_user_func_array() expects parameter 1 to be a valid callback, non-static method WP_Feed_Cache::create() should not be called statically	1	wp-includes/SimplePie/Registry.php:215	SimplePie_Registry->call()
 wp-includes/class-simplepie.php:1313
SimplePie->init()
 wp-includes/feed.php:703
fetch_feed()
 wp-content/plugins/google-sitemap-generator/sitemap-core.php:2117
GoogleSitemapGenerator->GetSupportFeed()
 wp-content/plugins/google-sitemap-generator/sitemap-ui.php:762
GoogleSitemapGeneratorUI->HtmlShowOptionsPage()
 wp-content/plugins/google-sitemap-generator/sitemap-core.php:2199
GoogleSitemapGenerator->HtmlShowOptionsPage()
 wp-content/plugins/google-sitemap-generator/sitemap-loader.php:260
GoogleSitemapGeneratorLoader::CallHtmlShowOptionsPage()
 Unknown location
do_action('settings_page_google-sitemap-generator/sitemap')
 wp-admin/admin.php:222	Plugin: google-sitemap-generator

What now? anyone?

Ok so I figured out my mistake almost as soon as I posted my last comment… DOH!

I’ve correct the code in my previous post to reflect correct code… I’ve yet to try to see functionality is good.

I’ll get back with more updates.
Hopefully it helps someone else

Here’s a small update to my trials:
I’ve tried to add the earlier code to my child theme’s functions.php with no visible change. I tried it as initially posted here and as I wrote it in my previous comment, also without seeing the option to translate in the CPTs pages

Any ideas?

@takayukister @mikylucky Hey guys, I came across this support question when I ran into something similar myself and was wondering if you could detail this a bit as I’m not sure I understood how you solved it.
So I’m using a theme that has at least a couple CPTs (I only need 2 of these to be available in another language) and I’m also using woocommerce.

If my understanding is correct, I’d have to use in the functions.php of the theme and somewhere (to be determined). How would this code need to be adapted to work for multiple CPTs since this is for just one.

add_filter( 'bogo_localizable_post_types', 'custom_bogo_localizable_post_types' );

function custom_bogo_localizable_post_types( $post_types ) {
	$post_types[] = 'your_cpt_name';
	return $post_types;
}

Would this work?

add_filter( 'bogo_localizable_post_types', 'custom_bogo_localizable_post_types' );

function custom_bogo_localizable_post_types( $post_types ) {
	$post_types[] = 'your_cpt_name1';
        $post_types[] = 'your_cpt_name2';
        $post_types[] = 'your_cpt_name3';
	return $post_types;
}

$post_types[] would be an array of the 3 names given?

Thank you!

• This reply was modified 8 years, 1 month ago by orangeworx.
• This reply was modified 8 years, 1 month ago by orangeworx. Reason: corrected code
• This reply was modified 8 years, 1 month ago by orangeworx. Reason: Corrected