Balint Toth

Hello!

Try to replace the .forum-archive to .forum everywhere in your code. This should solve your issue on all forum pages.

If you have any other questions, just feel free to ask them here.

Cheers,
Toth Balint BT

Hello!

You were right, the slider div has a box shadow property. This CSS code should get rid of it:

#slider{
	-webkit-box-shadow: none!important;
	box-shadow: none!important;
}

You should install Simple Custom CSS plugin and paste the above code to Appearance->Custom CSS.

Let me know if this worked, and if you have any more questions.

Cheers,
Toth Balint BT

Hello!

Could you please post a link to your site? I would like to give it a look…

Cheers,
Toth Balint BT

Hello!

As far as I know, WooCommerce adds some specific template pages when you install it, so it is possible that this is the cause. However, I think it can be easily solved with some custom css modifications.

For some reason the link to your website is not visible, so please post it again so I could take a look.

Cheers,
Toth Balint BT

Ok, it looks like we have overcomplicated this, so I apologize for this.

The answer for your question: no. Everything is on your server. We are downloading the files from a remote server when we install a theme, but from that point on, the files are completely on our server. However, as for plugins, themes also get updates occasionally, and when that happens, WordPress notifies us, and the updates can be downloaded and installed automatically by WordPress, we just have to click a button. And this is a good thing.
Whenever you update your theme, WordPress deletes all the files in your theme’s folder, and downloads the new version’s files from the central WordPress server. And there lies our problem, because WordPress has absolutely no way of distinguishing our modifications to the theme from the original files, and it deletes everything on update. This is why people use child themes, so you update the parent theme, but everything you have modified, stays intact. Now here the problem is, that the designer who created the Church theme, has also done this, he also created a child theme for a theme called omega. And he named his child theme Church. So basically when you have downloaded the theme, you have downloaded it together with the theme omega. So Church is a child theme, and you cannot create a child theme for a child theme.
So I am not 100% sure about this, but because the Church theme is in the WordPress central theme database (meaning you can find it if you search for it in WordPress Dashboard->Appearance->Themes->Add New Theme), it will get updates eventually from the designer. And when you update, you would loose any modifications you have made to it.
Considering this, I only see one option. Because the Church theme is already a child theme, you don’t have to create an other child theme, use it like THAT is the child theme, add modifications, and so on. Of course, the style.css file is not empty, so just add your code to the end of the file.
The most important thing is to never update the Church theme, if you get a notification that it has updates. This way, you can make sure that the modifications you make to the Church theme won’t get overwritten.

I hope this makes sense, if you have any questions, feel free to ask.

Cheers,
Toth Balint BT

These are the necessary steps for you:

1. On your webserver’s files, create a new folder called preus-child in /wp-content/themesso it is beside the preus theme’s folder. It should look like this:

wp-themes
    preus
    preus-child

2. Inside the preus-child folder, create a file called style.css
3. Paste this code to the file you have just created:

/*
Theme Name: Preus Child
Theme URI: http://inkhive.com/product/preus/
Author: Rohit Tripathi
Author URI: http://inkhive.com
Description: Preus Child theme
Version: 1.0
Template: preus
*/

@import url("../preus/style.css");

However, there is one important thing. On my test site the Preus folder’s name in themes is has a capital P. If your’s is not, just copy and paste the above code as it is. If your theme folder also has a capital P, you will have to modify the above code on 2 places:
Template: Preus and @import url("../Preus/style.css"); so they have capital Ps also. Please don’t try to rename the folder name, because it will break your theme.

4. Inside the preus-child folder create the category.php file, and paste the code that I have posted earlier.
5. Inside WordPress Dashboard, go to Appearance->Themes, there should be the child theme listed (without a screenshot image, what is completely normal). Activate the child theme.
6. Check how your site looks like on the Running page 🙂

There is not much difference to it if you use Dreamweaver or other tools. If you need any help, or have any questions, just let me know.

Cheers,
Toth Balint BT

In the church theme’s style.css it says Template: omega on line 12, this is why it is a child theme. The [parent]-child is just a naming convention, WordPress does not needs the parent theme’s name to be present in the child’s name to work.

Ok, here is the code necessary for your category.php file. It may need some tweaking, so whatever you need changing, just tell me and I am happy to help.

<?php

get_header(); ?>
<div id="primary" class="content-area col-md-8">
		<main id="main" class="site-main" role="main">

		<?php if ( have_posts() ) : ?>

			<?php /* Start the Loop */ ?>
			<?php while ( have_posts() ) : the_post(); ?>

				<?php
					/* Include the Post-Format-specific template for the content.
					 * If you want to override this in a child theme, then include a file
					 * called content-___.php (where ___ is the Post Format name) and that will be used instead.
					 */
					get_template_part( 'content', get_post_format() );
				?>

			<?php endwhile; ?>

			<?php preus_pagination(); ?>

		<?php else : ?>

			<?php get_template_part( 'no-results', 'index' ); ?>

		<?php endif; ?>

		</main><!-- #main -->
	</div><!-- #primary -->

<?php get_sidebar(); ?>
<?php get_footer(); ?>

Here is a demo how it works on a demo site.

Cheers,
Toth Balint BT