dankfresh

I was able to “work around” it by using this solution – https://stackoverflow.com/questions/16353899/changes-on-archive-product-php-doesnt-work

but… that goes against what the WooCommerce documentation says. Sort of scares me to use it.

I’m having the same problem. Strangely enough, eastbank’s suggestion at least let me figure out that it was native to my theme, but why I don’t know.

I switched to twentytwelve, made a woocommerce/archive-product.php file, override worked fine.

Go to my theme, start from scratch, do the same thing, override does not work at all.

This is a custom theme, so I have a woocommerce.php file in the root of my theme folder, which replaces the loop with <?php woocommerce_content(); ?> and then I declare support in the functions.php file like Woocommerce suggests here – https://docs.woothemes.com/document/third-party-custom-theme-compatibility/

THATS IT.

Again, even stranger, the only file that I haven’t been able to successfully override in my theme is archive-product.php. Everything else works!!

These are all according to WooCommerce’s docs, so I don’t know what could cause the override not to work in my theme. Would love to know.

So, didn’t realize this but product_cat can take multiple arguments, separated by commas. This acts like an “OR” statement, though, and doesn’t produce the desired effect. I would like to find products that specifically belong to both.

Had the exact same thing happen. May 8th. No clue as to why. I ended up making a new Twitter app, getting a new APP key, etc, and trying again. It’s the strangest thing, if I change the amount of Tweets to show in a feed, say 5, it will go get the most recent Tweets, but then never update. If I go back to 1, where I had it before, it goes right back to the 1 tweet I had May 8th. It’s almost like it caches the request.

get_attachments_by_media_tags('media_tags=NAMEHERE&return_type=li&size=full');

and the options are thumbnail, medium, large, and full.

Hey roblagatta. Yes, thank you for following up! Excellent support.

Well, I accomplished a little something….

I would prefer the slug, but I duplicated + renamed the tribe_meta_event_cats(); function (located in plugin /public/template-tags/general.php) to this :

function tribe_meta_event_cats_short( $label=null, $separator=', ')  {
	if( !$label ) { $label = __('', 'tribe-events-calendar'); }
	$tribe_ecp = TribeEvents::instance();
	$list = apply_filters('tribe_meta_event_cats', get_the_term_list( get_the_ID(), $tribe_ecp->get_event_taxonomy(), '', $separator, '' ));
	return strip_tags($list);
	}

The important thing is it returns the category name(s) and I used strip_tags() to remove the links. Then, on my single.php page, I store that to a variable and echo it whenever I please. I’m sure there is a better way to accomplish though….

Thanks, although the sitemap generator is not the cause of this issue. Turned out it was malformed links that were placed in posts throughout the site.

You need to have “https://” place before every link and it has to be the entire URL. If it’s just “www.thesite.com” in your then Google bots will read this as a page name in your root directory and thus it results in :

“https://www.yoursite.com/blog/postname/www.yoursite.com”

So, I fixed it. Thanks.

Yea, the links are all set up fine on the site. I use xml-sitemaps.com as a generator. It’s always worked fine.

Yea I uploaded index.php a few times, and the entire WordPress package to see maybe if that was the case.

Still waiting to hear from Network Solutions.

From what I’ve read, this could be a problem on their part, as a lot of people have experienced this with NetSol.

Thanks. Those are some pretty good ideas.

I’m hosting through 1&1 and they specifically state you can’t increase your memory allocation beyond 30M, but for a file that’s 3.08MB I would guess this wouldn’t consume that much. Perhaps I need to give phpinfo a shot and see what’s happening.

In that forum you linked me to, someone suggested using image destroy to free up memory. Have any experience with this?

ok, well it’s simply a syntax error.

go into your ftp file editor, go to line 658, and erase the & in the line
foreach ( $wp_posts as &$item )

i don’t know how to mark this to resolved, otherwise i would.

yea, same error upon activation as well. anyone encounter something similar?