johpg

@troy7890: Thanks for the advice about WebDefender.

It found some PHP files in the wp-contents/uploads directories that Wordfence missed.

If you put
“\x2fh\x6fm\x651\x2fm\x61v\x65r\x69f\x35/\x70u\x62l\x69c\x5fh\x74m\x6c/\x73i\x67n\x73o\x68i\x6f/\x77p\x2dc\x6fn\x74e\x6et\x2fg\x61l\x6ce\x72y\x2ff\x61v\x69c\x6fn\x5f4\x641\x622\x66.\x69c\x6f”
into UNPHP.NET it decodes to this:
/home1/maverif5/public_html/signsohio/wp-content/gallery/favicon_4d1b2f.ico

This is a malicious file that should be deleted.

Check Settings-Users for any Administrator accounts that you don’t recognise and delete them.

Have posted issue to GitHub:

Job Expiry & Expired Job Deletion Not Working #983

Yep still not working.

If I run job_manager_check_for_expired_jobs from the WP Crontrol plugin I get this:
“Successfully executed the cron event job_manager_check_for_expired_jobs.”

However the event is not doing anything.
There is a job that should be set to expired and yet the status remains active.

You can do this via CSS:

.search_jobs { display: none; }

Just found the fix here:
https://www.ads-software.com/support/topic/fatal-error-2309/

Basically reset and re-authorise the plugin.

I have the exact same issue – same error message.

I’ve contacted the theme author about this and here is their reply:

“your issue is the front end template which is not compatible, and I’m sorry but this theme front end isn’t compatible with the wp-ecommerce. you may need to create your own product archive page. I don’t know if wp-ecommerce have this template stuff, but in woocommerce you can create your own template you just need to make sure the template is build like the theme html structure.”

So I need a “product archive page”.

I’m totally confused about how WP eCommerce combines with a theme to produce the output.

What do I call this product archive page to ensure that it is called when I’m listing a product category?

The page is https://sureknowsomething.com/shandora/products-page/ ?and that page contains this shortcode: [productspage]

Okay, I’ve found out why remove_actions don’t work on the child theme.

The child theme’s functions.php loads before the parent theme’s functions.php
This means a remove_action in the child theme is trying to remove something that hasn’t yet been loaded by the parent.
See https://www.marcusnyberg.com/2012/02/03/using-remove_action-in-a-wordpress-child-theme/

However, the solution provided in the above reference creates a bigger problem.

I added this code to my child theme’s functions.php:

function removeParentFunctions() {
remove_action( 'highwind_footer', 'highwind_credit, 20 );
}

add_action('after_setup_theme','removeParentFunctions');

This caused the “White Screen of Death” on my site. A completely inaccessible site. I had to access functions.php by FTP and remove the above code for my site to become visible again.

The WSOD was also reported here:
https://www.ads-software.com/support/topic/change-the-footer-text-and-change-the-sidebar-to-the-left

That thread (incorrectly marked as resolved) is about the same issue as I am reporting in this thread.

Current status:
The theme author is giving incorrect information regarding the use of remove_action in a child theme.
The apparently correct way to use remove_action in a child theme completely breaks this theme.

Anybody have any ideas?

Adding
remove_action( ‘highwind_footer’, ‘highwind_credit, 20 );
to functions.php of my child theme DOESN’T WORK for me.

In fact adding adding “remove_action” for anything into functions.php of my child theme has no effect.

The only way I can make changes is to comment out the “add_action” line in theme-actions.php in the parent Highwind theme.

Why isn’t remove_action working when used in my child theme?

I can’t get this to work:

<?php $id = get_parent_category();
 if ($id) {
 include(TEMPLATEPATH . '/template' . $id . '.php');
} else {
 include(TEMPLATEPATH . '/a_different_template.php');
 } ?>

Exactly which file, and in what position in the file, does the code go?

I think the thread at https://www.ads-software.com/support/topic/127550 has the answer, but I can’t make it work for me.

You put this in functions.php to work out whether you are in a parent category or not:

function get_parent_category() {
 global $wp_query;
 $category = $wp_query->get_queried_object();
 if ($category->category_parent) return $category->category_parent;
}

Then you add this to your archive.php:

<?php $id = get_parent_category();
 if ($id) {
 include(TEMPLATEPATH . '/template' . $id . '.php');
} else {
 include(TEMPLATEPATH . '/a_different_template.php');
 } ?>

However, this isn’t working for me – I’m assuming I’m not putting the code in the right place.
Where exactly in archive.php do you put the code?
Or maybe it doesn’t go in archive.php, but somewhere else?