Forum Replies Created
UPDATE: I solved the issue.
I simply used the iframe code given by Vimeo instead of the simple URL.
But you should check this out anyway.
Here is the link: http://berza.it/dev/linea-parrucchiere-estetica/
It’s a development environment and at the moment there are only two portfolio items, but the filter should show up anyway..
Also, I noticed I posted in the wrong section: actually the theme is Flagship and not Flashlight.
Aww, this kind of software looks awesome. I downloaded jitbit’s one for Mac, I hope it’s powerful enough :)
I would Google that, but this is the kind of question you don’t easily find a certain answer to: besides a backup of what is working now, I’d like to have also a live version of it somewhere when I erase everything. This is mainly so that I can copy things from the old version to the new one without having to write all down in the beginning (and being sure to forget something).
I mean, could I simply move everything to a sub-folder? Or, since I have only 1 db with this hosting plan I could even move to another spare domain I have on my own. If I do so, what references should I change and when? I know WordPress is a little delicate when moved all around, as I already had some problems when having to deal with this
Ok then, what are you suggesting by “using a lot of macros”?
How would you proceed to do it fast and without too much pain for myself? :)
As I wrote you, I tested the site and switched back to my old one to get back on the issue.
This time, I decided to take a step back and try to understand when things break 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 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: http://d.pr/f/y6Z1
Please, I’d like to have your opinion on this. I think this is as deep as I can get trying diagnosing the problem.
If this leads to nothing, I’ll probably leave WPML for a while, and perhaps do this with a double-installation setup.
Unless you can suggest me a way to wipe everything to make a true clean install but still be able to re-import most information after this (I mean pages, portfolio items, and all the linked media files). Something that should work like the “demo data import” function.
I’m now going to post a similar explanation on the WPML forum to see if they could say something, too.
Given the dynamics you’re talking about I’m more and more suspicious around the qTranslate Importer plugin (http://wpml.org/documentation/related-projects/qtranslate-importer/ ) I used to generate the translated posts. It might be that it has some issues creating that _avia_elements_avia_options_flagship_en on posts.
However, when I tested with new page, portfolio item, portfolio category and theme settings created manually, they didn’t work, so that’s odd.
You won’t be able to create a new database, but you can proceed renaming and inserting the new tables if you can do that with a WordPress plugin. Otherwise just send me the script and I’ll do it manually via phpMyAdmin (perhaps I should send you the credentials for that, too)
It’s really awesome to see that your fresh build is working fine, it makes me hope we’ll reach a solution in the end.
I tried again to exclude any possible issues:
- I tried going back to default permalink structure (with the appended query string), both in the WordPress settings and in the WPML settings
- I tried disabling all plugins but WPML
- I tried comparing the original theme folder downloaded from themeforest with the live one using Kaleidoscope trial (kaleidoscopeapp.com), and I found only some minor tweaks I did that do not have anything to do with this issue (changed an image, added some header code / footer signature, and added a few functions needed for a fast custom addition to the site)
The thing about Multilingual Content Setup you show on 4:23 in your screencast. I don’t have that.
I mean, I have the same custom field called “_avia_elements_avia_options_flagship” for both the English and the Italian version of my pages.
Is this an hint of something else we need to check?
Anyway, I’m now sending you the credentials, thanks a lot for your support.
I did as you suggested.
[lines 4 to 529]
[lines 532 to 3985]
[lines 3996 to 4030]
where all the code after </admin-texts> was in the original .xml file.
Is it correct?
Well, the problem is not solved :(
I followed your instructions and found the line you were asking for
INSERT INTO 'wp_options' VALUES (196, 'current_theme', 'Flagship', 'yes');
I tried generating the xml with the php file provided by Harshard, but it reported an error:
Warning: Invalid argument supplied for foreach() in /htdocs/public/www/create_wpml_config.php on line 23 </key>
Then I tried the xml file you provided via pastebin, but it again doesn’t solve my problem. I don’t know where to look to understand whether it changes something else, but certainly the main issue is not resolved.
Also, I asked Harshard what you wanted to know, and I’m currently waiting for an answer ((Purchase code hidden if logged out) /#post-116661?affiliate_key=K9b6X1wRp9SS”>http://wpml.org/forums/topic/ (Purchase code hidden if logged out) /#post-116661 )
I changed that line to
"std" => "product",
but I still can’t see anything happening in the pages (supposed to be) displaying portfolio items or in the theme options.
I’d like to point you out again to the other forum’s suggestions: (Purchase code hidden if logged out) /#post-115652?affiliate_key=K9b6X1wRp9SS”>http://wpml.org/forums/topic/ (Purchase code hidden if logged out) /#post-115652
The file Harshad is referring to is this one: http://d.pr/f/nGi (a php file that generates an xml)
I have sent you email with a file attached, please follow the steps below:
1) Upload the attached file to wordpress root folder
2) This file will create a code for wpml-config.xml file.
3) Then execute the file using http://yourdomainname.com/create_wpml_config.php?option_name=<option_name>
4) Copy the code to your wpml-config.xml file
5) Upload the wpml-config.xml file to your themes root folder.
Note :: Replace <option_name> with actual option_name used by your theme.
He asks me to replace <option_name> with actual option_name used by your theme.
Do you have any idea what option the theme uses for this functionality?
I also noticed the theme already includes a wpml-config.xml file, but from what I can understand it looks like that file just tells WPML which elements have to be translated, and something about the styling of the language switcher…
Thanks a lot for your effort.
First of all, I tried again to filter rewrite rules with a more complex invalid URL, and now only the following rule shows
(.?.+?)(/[0-9]+)?/?$ index.php?pagename=$matches&page=$matches page
Second, I carefully followed your instructions trying to setup a page and portfolio items in different languages, and the language switch has no problem at all.
So, I set up:
- A new page, original in Italian and translated in English
- A new portfolio item, same languages
- A new portfolio category, same languages. Assigned to the portfolio item
- A new portfolio “rule” in Flagship > Theme Options > Portfolio using the new category as a filter and the new page as the “display page”
It still doesn’t work, as the only issue is still the one with – I guess – the page slug used for portfolio items, that has some problems: http://d.pr/i/xT6o (screenshot)
I’ll report soon.
I did what you suggested.
The first time I entered the plugin page, it showed 105 rewrite rules, none was red.
I checked with a simple invalid URL (like http://domain.name/bababa ), and there are 2 rules that match:
(.?.+?)(/[0-9]+)?/?$ index.php?pagename=$matches&page=$matches page
([^/]+)(/[0-9]+)?/?$ index.php?name=$matches&page=$matches post
Then I flushed the rules, but nothing changed: the new list is still made of 105 rules, that look the same as before, and filtering by an invalid URL still gives the same result.
Thanks for your work,
I asked for help with this issue also to the WPML support staff, and they are giving some hints that maybe could be useful also for your analysis of the issue.
The strings that are part of the options that the plugins or themes save in the wp_options table.
When themes and plugins use get_option, they read values from the wp_options table. WPML can filter these calls and provide translation to the values of these options.
For this you can create a language configuration file, which tells WPML which Admin texts you want to translate.
Could this be a useful hint?
Would you be able to translate this into something to do practically? I’m a little into the technical details, but not enough for this (and I wouldn’t be asking for help otherwise) :)
No, it doesn’t :(
Still, setting Default permalinks AND disabling WPML solves the problem.
EDIT: also, if this is somehow useful, the qTranslate to WPML Import plugin ( http://wpml.org/documentation/related-projects/qtranslate-importer/ ) wanted me to add some URL redirects to the .htaccess file in the root folder of my website. I tried commenting and also removing these RewriteRule instructions, but nothing changes with respect to this issue.