[Resolved] Issue in retrieving portfolio items

Of course, you can find them as attachements.

Thanks, this looks really relevant.

Would you be able to translate this into a practical action for me? 🙂
I also asked in the theme's support forum, as they could have the complementary information.

Dear Harshard,

I asked the theme developers and they guess the <option_name> should be current_theme (hidden link)
Trying to use that option into the create_wpml_config.php file gives this output:

<wpml-config>
<admin-texts>
<key name="current_theme">
Warning: Invalid argument supplied for foreach() in /htdocs/public/www/create_wpml_config.php on line 23 </key>
</admin-texts>
</wpml-config>

However, Nick on the other forum is asking:
<blockquote cite="Nick on Kriesi support forum">Ask Harshad if the php file he sent you accepts: (a) transient option fields and whether they should be added

He also gave me this file (http://pastebin.com/1jRS8XWh) to try to replace the theme's original xml file, but it doesn't work 🙁

Dear Harshard,

I sent you an email with the details you asked for.
In the mean time, the latest xml I generated (hidden link ) activated a lot of new strings in the WPML > String translation menu.

I tried translating the item that seems nearer to my problem, which is an item named "[avia_options_flagship][avia]portfolio-slug", whose string is "prodotto" (italian for "product"), that is the one I placed into my theme options (see screenshot in the previous post). However, I can't see how this could solve the issue and in fact it doesn't.

What is your expectations about what to do next?

I will now try not to touch anything else so you can see everything with your own eyes via FTP and wp-admin.

Dear Harshad,

I'm not sure where exactly I should check to see if the translated text is displayed correctly.
Certainly, this fix did not solve the portfolio display issue.

You could also see it yourself by going to pages like:
• hidden link (translated into hidden link )
• hidden link (tr. into hidden link )
• hidden link (tr. into hidden link )
and trying deactivating WPML.

Dear Harshad,

I took a step back.
You can see how I proceeded in the Kriesi support forum here: hidden link.

Since a fresh install shows no compatibility problem between Flagship theme and WPML, I decided to understand when things broke for me in the first place.

So I reverted to the original DB backup that I made before even starting the migration from qTranslate to WPML, when everything was working fine.

I used a plugin (your qTranslate importer with WPML disabled) to clean wp_posts content from qTranslate junk.

FYI, qTranslate simply translates content using this structure:

<!--:it-->Some text in Italian<!--:--><!--:en-->Some text in English<!--:-->

and selectively displays the right content based on the language you choose. I discovered later that this approach is too basic and does not allow for a complete translation of a website based on the Flagship theme.
The cleaning was simple. After that, I checked all around the wp-admin for stuff that still had the qTranslate syntax, and in the end I directly searched the database to find any occurrence of the :it/:en structure and fixed them manually. Also, I deleted the freshly created entries in the wp_postmeta table that assigned a _qt_cleaned meta information to all the posts that were cleaned.

At this point, my DB looks fine, or at least there is a perfectly reasonable number of records and the ones I can understand make sense.

Here, I activate WPML. Just activate it. It means it just creates a bunch of db tables but doesn't actually do anything to the functionality of the site (i.e. the portfolio display works).
--> I made a DB backup here

Now, I start the setup. Which means I open WPML settings in the admin area and it asks me which is the main language. Italian is already selected, and I click "Next".

BAM! Now, and from now on, the portfolio display is broken.
--> Second DB backup here

I ran a diff software to see what changes. At this point, my knowledge is no longer enough to understand what is getting broken, but I hope someone else's could be.
You can download the diff "report" along with the two DB exports (just before and just after the key moment) here: hidden link (I'm now going to email you this, too)

Please, I'd like to have your opinion on this. I think this is as deep as I can get trying diagnosing the problem.

Thanks,

Michele

Thanks Harshad,

The first time I ran the importer I saw that screen, and I also copied the content into the .htaccess file.
It was still problematic.

However, thanks for your support.
The client and I decided to go online with Italian only for the moment, and review later the possibility of adding the second language. For that, we'll probably make a fresh install and do "all" from scratch.