This topic has 4 voices, contains 15 replies, and was last updated by  TB Support WP 3995 days ago.

Child Theme Support

ThemeBurn Support › Forums › WordPress Themes › Shoppica WordPress Theme › Child Theme Support

This topic has been marked as not resolved.

Hello,

Unfortunately after purchasing your Shoppica WordPress theme today we’ve found that it isn’t compatible with child themes. We’re investigating the possibility of continuing with the theme regardless but if necessary would you be happy to offer a refund?

If child theme support is around the corner then we might be able to continue.

We look forward to hearing from you.

Kind regards,

Conrad
 ceg
May 13, 2013 at 2:07 pm #23095

Hello Conrad,

We are now working on the child theme support. Hopefully it will be ready in a couple of days. We will then resubmit Shoppica WP in ThemeForest and you will be able to download the new version.

We will also create an announcement here.

Best regards,
Svetoslav

ThemeBurn team
 TB Support
May 16, 2013 at 10:59 am #23239

Great, thanks Svetoslav, I’ll wait for your announcement.
 ceg
May 16, 2013 at 12:03 pm #23242

Hi Svetoslav,

I was hoping to get an update on how the child theme support is going. Please could you let me know?

Many thanks,

Conrad
 ceg
May 21, 2013 at 7:51 pm #23424

Hello,

Attached is the patch for Child Theme support. We will include this with next theme update.

Best,
ThemeBurn team
 TB Support WP
May 22, 2013 at 3:36 pm #23450

Great, thanks very much.
 ceg
May 22, 2013 at 6:04 pm #23459

Glad we’ve helped :)

Best,
ThemeBurn team
 TB Support WP
May 23, 2013 at 3:25 pm #23497

Hi! ceg:

Did the patch worked for you?

I made a clean install of WordPress 3.5.1 with a clean install of Woocommerce 2.0.10 and a clean install of Shoppica Theme version 1.2.2

Then I created the child theme for shoppica as described in the WordPress codex and applied the patch to the shoppica theme. I mean I overwrited files in shoppica folder with files included in the patch file.

I activate the child theme then, and Layer Slider Option is not present in the admin panel. So no way to configure it.

Did this worked for you?

Thanks for your time.
 dogdayfear
June 4, 2013 at 6:11 pm #24035

Hi there,

Unfortunately I haven’t had a chance to make much progress yet but that should change in the next few days. If that’s not too late I’ll let you know how I get on.

Thanks,

Conrad
 ceg
June 4, 2013 at 6:18 pm #24036

@dogdayfear, @ceg:

We tested child theme patch on few different installations, and we find that on one installation LayerSlider didn`t loaded. Attached is the new version of the patch.

@dogdayfear, maybe you have the same problem?

Best,
ThemeBurn team
 TB Support WP
June 4, 2013 at 7:55 pm #24041

Yes, that was my problem.

With the first patch no Layer Slider options section in admin area. And in front page shortcode was showed instead of the slide.

Unfortunely this version of the patch does not corrects the errors for me.

Options in admin are unformatted and slide now shows but … well just take a look to the attached files.

I am using latest version of wordpress, latest woocommerce and your theme. No other plugins. Nothing more.

Latest Google Chrome as browser.
 dogdayfear
June 5, 2013 at 6:05 pm #24064

Hello,

We are working on the problem, and when we have a solution will post it here.

Best,
ThemeBurn team
 TB Support WP
June 5, 2013 at 11:03 pm #24072

Ok. I will stay tuned here.

Hope you find a solution ASAP.
 dogdayfear
June 6, 2013 at 11:15 am #24077

@dogdayfear,

Attached is new version of the patch, we tested it here and everything is working on our test installation.

Please post if you have any problems.

Best,
ThemeBurn team
 TB Support WP
June 6, 2013 at 5:01 pm #24086

Child-Theme seems to work.

But I have now another problem. Ajax ‘add to cart’ option dows not work as shown in Themeforest Demo. It does not show pop-up message.

Is this cause woocommerce does not support it?
 dogdayfear
June 7, 2013 at 2:43 pm #24135
Viewing 15 posts - 1 through 15 (of 16 total)
1 2
  • You must be logged in to reply to this topic.