0 items - $ 0
- No products in the cart.
This topic contains 12 replies, has 4 voices, and was last updated by James Wooldridge 1 month, 1 week ago.
Viewing 13 posts - 1 through 13 (of 13 total)
-
Posts
-
Hey all,
A big change since the old version is that the new version should also support child themes. Have any of you played around with that yet? Everything working well for you there?
Kevin
Kevin,
G’Day again.
I wasn’t aware that the new version supported a Child Theme, so haven’t tried that yet.
Will try it out for you. But it shouldn’t be any real issue, as if a Child Theme is set up properly, whether independently of the theme (which i do for those that don’t provide a separate Child Theme) or one that comes with a Theme then there should be no issues.
Cheers,
Michael.
Hey Kevin
Great news my man! This is getting better all the time.
Child theme it is and initial indications… working like a charm!
Whoooo hooooo this is good!
James
Kevin,
G’Day again.
Sorry to be the bearer of a potential issue, but I can’t get the Child Theme to work with the latest available version. It appears that all the formatting for the front page (as only have the one page operating at this stage) is all stacked one after the other.
Let me explain the steps.
1. Downloaded the latest version of Mikmag from ThemeForest - I have a valid purchase.
2. Installed Mikmag on a clean version of WordPress (v3.5.1) on my LocalHost using Destop Server, but did not activate.
3. Created a Child Theme reference in wp-content/themes/name of child theme.
4. Created a style.css file in the child theme folder. Only content in the file was references to use the Mikmag theme.
5. Activated the Child Theme in site backend.
6. Created two Pages and set up the main menu system to have these two pages showing.
7. Viewed site and all content appears stacked one after the other - the menu items were one after the other, and the four footer items were all one after the other.
8. Deactivated the Child Theme and then activated the Mikmag theme.
9. Set up the menu system again.
10. Viewed site and all appeared in the right positions.I’ve attached the style.css file from the child theme for you to see,
I’ve set up child themes for other themes using this same style.css file (obviously some details do change) and never had any issues.
Cheers,
Michael.
Kevin,
Further to my comment above, I even tried adding the ‘import’ command to the child theme style.css fie without success. The commands were:
/* =Import Styles
* WARNING: Do not remove these stylesheets
————————————————————- */
@import url(‘tdframework/css/normalize.css’);
@import url(‘tdframework/css/base.css’);
@import url(‘tdframework/css/responsive.css’);
I’ll be interested to see what the developer(s) come up with. Maybe they can provide an actual child theme folder and files.
Cheers,
Michael.Hmm, that’s quite strange. Mostly as the other beta testers appeared to be successful with this.
Does the rest of the layout adapt to the Mikmag theme properly? Is it only the menus (main and footer) piling up that’s causing an issue?
If so, did you have the menus set up using Appearance -> menus when trying this? Not having done so often results in this stacking behaviour.
Kevin
Playing The Devils Advocate tonight
Hi Guys, I just created a child theme w/o any issues.
@import url(“../mikmag/style.css”);
@import url(‘tdframework/css/normalize.css’);
@import url(‘tdframework/css/base.css’);
@import url(‘tdframework/css/responsive.css’);rtl.css
sytle.css
screenshot.pngWorking perfectly using 3.5.1
Respectfully commented.
Have a better one!
James
PS: It is the release version MikMag 2.0 with functioning child theme.
James,
G’Day.
Okay, I’m still having an issue getting a Child Theme to work.
So, can you post the style.css that you have used to create a Child Theme for Miknag.
Thanks.
Michael.
Hi Michael:
1) In your separate child folder (located in the themes folder) add the following files:
style.css
/*
Theme Name: YourSiteName
Description: whatever you want e.g. version
Author: YourName
Template: yoursitename(optional values you can add: Theme URI, Author URI, Version)
*/@import url(“../mikmag/style.css”);
@import url(‘tdframework/css/normalize.css’);
@import url(‘tdframework/css/base.css’);
@import url(‘tdframework/css/responsive.css’);
@import url(‘tdframework/core/shortcodes/shortcodes.css’);rtl.css
/*
Theme Name: YourSiteName
Template:Right to Left text support.
*/
@import url(“../mikmag/rtl.css”);screenshot.png of your own branding
You are good to go! Enjoy!
Have an awesome weekend.
James
James. <br>
G’Day and many thnaks for your prompt reply. Much appreciated. <br>
However, unfortunately your solution, which I understand have implemented on previous themes, etc., does not work here. You can see here how the site is looking: http://tourdetwowheels.com ! <br>
Very frustrating ! ! ! <br>
And just a correction - in your generic style.css file, you need to have “mikmag” as the Template option, as WordPress needs to be looking for the overarching theme and its options - I believe. <br>
Any additional help you can provide would be greatly appreciated. <br>
Cheers, <br>
Michael.
Hi Michael.
The child themes I use are never named after the parent, thus the child bears its own naming convention. The example above is from a different name and functions perfectly with a lot of modifications made in the child style.css.
From your example, it would appear required files are not being called.
If you using hash symbols ‘#’ as part of your numbering or referencing systems remove them and everything will work. In addition remove all spaces using only _ or - as separators for easy reading . No empty spaces.
There appears to be additional code added to your lines:
I see a #2 reference being used as well as the following…
http://tourdetwowheels.com/wp-content/themes/tourdetwowheels/%E2%80%9C../mikmag/style.css%E2%80%9D”
style.css”
normalize.css’
base.css’
responsive.css’
I noted <br> marks at the end of your sentence punctuation above thinking they were perhaps you own decorative style. If they are not, then I would say your system is injecting erroneous characters and numbers.
Resolve the errors identified and your site should work perfectly unless there are other ghosts that need to be exorcized.
Let me know.
James
Hi Micheal.
I was about to close your link example and something told me to check further links. What I am seeing is the style.css file being called from what appears to be the uploaded folder location misidentified: http://tourdetwowheels.com/2013/06/#2
An educated guess is your site file structure is badly corrupted if the above example is an indication with numerous other anomalies pointing to the same file location.
If this is a new setup delete everything, drop the db tables and start a fresh install. Upload a fresh copy of WP, Mikmag 2.0 via FTP and you will be able to set up your child theme in a snap. Don’t use whatever you used to initially set it up.
If you have uploaded images and plugins you may want to download their respective folders before you delete everything. The same goes for pages and posts using the export xml feature.
Once you are happy you have backed up what you want, delete everything including all file structures. Reinstall your plugins from the WP repository in case there is a gremlin lurking somewhere in your previous files.
If a backup and restore system was in use, it is probably the suspect generator for all of your problems.
Use FileZilla or the FireFTP add-on if you are using Firefox. Use Notepad++ for your file editing so you can edit the files directly on your site using the file preferences for default programs.
Mikmag is a “Rolls Royce” of themes and well written. Something else is causing you to pull out your hair and run down the street screaming.
Let me know what your investigation reveals.
Have a great evening.
James
Viewing 13 posts - 1 through 13 (of 13 total)You must be logged in to reply to this topic.