mdugre

Until I can figure out what the problem is or someone on this forum can tell me what I’m doing wrong, I reverted back to Customizr version 3.3.20 which works fine.

Cheers,

Marc

That’s exactly what I mean Chris. Thanks for the link. I’ll use the info here to see if it solves the issue.

Cheers,

Marc

Yes I do and I cannot not have one on this site.

To be honest, the string translation isn’t such a big deal as I have done both English and French pages on my site. It would just be a nice to have.

Also, although on some pages, WordPress does do the translation to French through the built-in *po files, there’s one page (update user profile through front-end (member restricted access only) page) where it doesn’t. Still working on solving that one

looks like crap. email me at [email protected] and I’ll send you the file

How do paste the image here exactly? I don’t seem to be able to paste a print screen here

Correct Chrystl

Hello Chrystl,

Here’s what I had in settings > Permalinks > Common Settings

Post name https://www.datatelcom.com/sample-post/

Changed to Custom Structure https://www.datatelcom.com/%postname%/ and hit save. It reverted back to Post name https://www.datatelcom.com/sample-post/

In Settings > Languages > tab Settings: I can select what ever I want. Current setting is:

The language is set from the directory name in pretty permalinks

I also have the following enabled in that section:

– Remove /language/ in pretty permalinks
– Detect browser language When the front page is visited, set the language according to the browser preference
– Media Activate languages and translations for media

Inthe Synchronization section, nothing is selected

That’s what I did, yes

Good point

Quetas_admin when you say the following you are partially correct (I think)

According to the codex you can do it with any theme.

If you want to change more than just the stylesheet, your child theme can override any file in the parent theme: simply include a file of the same name in the child theme directory, and it will override the equivalent file in the parent theme directory when your site loads. For instance, if you want to change the PHP code for the site header, you can include a header.php in your child theme’s directory, and that file will be used instead of the parent theme’s header.php.

The problem I see in doing this is that the parent header.php file becomes useless. The child themes’ version takes over.

This basically means that every time there’s an update, unless you copy the header.php file in the child themes’ directory and add back your modification to it, you’re S.O.L.

Which brings us back to square one

As I’m sure you know Andrew, considering it’s free, the Customizr theme is actually pretty good.

Themes and Co. is constantly upgrading it too. I wouldn’t be surprised if the author, Nicolas Guillaume, would add some header.php modification capabilities in the theme at some point.

Heck, there is an already an advanced option capability built-in allowing you to input custom CSS code. My next step is actually to see if I can do what I want using that feature

Thanks Andrew. Guess I’ll have to do some digging and maybe look at deployment tools\

Questas admin, appreciate the input but, if there’s a header.php file with the Customizr Child theme, I don’t see it

What I have on my screen when I select Customizr Child is the following

Templates

This child theme inherits templates from a parent theme, Customizr.

Theme Functions
(functions.php)

Styles

Stylesheet
(style.css)

And there in lie the problem. I want the updates to the parent theme reflected in the child theme.

In doing what you suggest, every time there’s an update to the theme, I’ll need to go in and copy paste the update code. I’m looking for a way around that

Huh? I think I’m missing something here. My understanding is that when there’s a theme update, potentially all files, including the header.php file, are modified.

If I copy the header.php file in my child theme directory, that file should also be modified, no? If this is indeed the case, that means that whatever modification is do will need to be re-entered. Is that not the case or I’m I missing something here?

Well, that’s easy enough BUT, in order to keep my modifications and my theme up to date, won’t I need to do this after each an every theme update?