indira14

Are there plans to make it compatible with WPML at all?

Here’s what I did to make it work:

Added content-single.php to my theme, with this code:

<article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
	<div class="entry-content">
		<?php the_content(); ?>
	</div><!-- .entry-content -->
</article><!-- #post-## -->

Added content.php to my theme, with this code:

<article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>

	<?php if ( !is_single() ) : ?>
	<div class="post" id="post-<?php the_ID(); ?>">

		<h1><?php the_title(); ?></h1>

		<?php the_post_thumbnail(); ?>

			<?php the_content('',FALSE,''); ?>

		<?php comments_template(); ?>
	</div>

	<?php // For single posts and pages, display the full content ?>
	<?php else : ?>

	<?php endif; ?>

</article><!-- #post-## -->

In single.php, the loop should be:

<?php while ( have_posts() ) : the_post(); ?>
			<?php get_template_part( 'content', 'single' ); ?>
		<?php endwhile; // end of the loop. ?>

I also added single-proof_gallery.php to my theme, also with this as a loop:

<?php while ( have_posts() ) : the_post(); ?>

			<?php get_template_part( 'content', 'single' ); ?>

		<?php endwhile; // end of the loop. ?>

Hope this helps!

Thanks, that worked. I guess I did it in the wrong order. Thank you!

Please forget my previous post. This e-mail problem has been solved and turned out not to be related to the short_open_tag.

Thanks for your reply. We’ve enabled short_open_tag and now it works nicely!

Will the next version of the plugin stop using short_open_tag? Might be a good idea considering:

; This directive determines whether or not PHP will recognize code between
; <? and ?> tags as PHP source which should be processed as such. It’s been
; recommended for several years that you not use the short tag “short cut” and
; instead to use the full <?php and ?> tag combination. With the wide spread use
; of XML and use of these tags by other languages, the server can become easily
; confused and end up parsing the wrong code in the wrong context. But because
; this short cut has been a feature for such a long time, it’s currently still
; supported for backwards compatibility, but we recommend you don’t use them.

Please reply. I can’t launch my site if this plugin is not completely translated. I have the latest version of both Gravity Forms and Gravity Forms (nl) but still the Next and Previous buttons are in English.

We did a similar thing to make the subcategories show. Glad you two ‘solved’ it too.

Still, I think WooCommerce should do something about this because this problem keeps coming back. Our structure was perfect, now we had do a unwieldy workaround to make everything show up correctly.

I have updated the plugins and re-activated WooCommerce Multilingual but still no products are added to the cart. It is not fixed in WooCommerce 2.2.3.