Do you mean the standard text strings like on the search page: http://www.volantexrc.com/cn/?s= (“If you are not happy with the results bellow please do another search”, etc.)? If yes you must translate these strings with a po/mo translation file. I’d suggest to generate the po file with Codestyling: http://wordpress.org/plugins/codestyling-localization/

Install the plugin, go to Tools > Localization and select “Themes”. Then search for “Enfold” in the list and click on “Add new language”. Afterwards select your language from the list and click the “create po-file” button. Click on “Rescan” to fetch all text strings. Then click on “Edit” and translate the required strings from the “avia_framework” textdomain. At least click the “create mo file” button next to the “Textdomain” selection dropdown (top left corner).

Or do you want to translate i.e, “ABOUT US”? If yes just open up the textblock element (seems to be part of a color section) and replace the text with your translation…

No, but you can change the “portfolio-item” slug on the theme option page (Enfold > General Settings). On the portfolio item editor page you can edit the permalink by clicking on the “Edit” button next to the permalink

Hi!

Sounds like a javascript issue/conflict. You can use the browser console to determine which script breaks the website.

Best regards,

Peter

It seems like the standard search query doesn’t work in your case. Eg

http://www.lighthousemktg.com.au/?s=test doesn’t work but the same search works on the demo page:

http://kriesi.at/themes/enfold/?s=test

Try following

1) Deactivate all plugins and check if the search works. If yes activate them one by one until the search doesn’t work again.

2) If 1) does not solve the problem upload all wordpress and theme files again. Use the latest versions (wp3.6 and Enfold 2.0.x).

3) If 2) doesn’t work go to Settings > Permalinks and hit the “save” button to flush the rewrite rules.

Just so you guys know, I think the big issue with Fontello is the encoding of the font files. I think a while back, Fontello switched its default from ASCII or Unicode to Private Use Area encoding — basically, the section of the Unicode range that intentionally has no characters assigned by default, so anyone can use it for their own thing without conflicts. My theory is Kriesi encoded his Entypo version as Unicode, and that’s the snag.

The “cartoony icons” are OS X’s (maybe others too) default emojis, because the PUA encoding of the font in this case means there is no “font override” going on for those Unicode characters, like there is when you encode as Unicode.

Unless I made a very stupid mistake and mixed up the files, I removed the Enfold default icon fonts, tried replacing them with PUA and ASCII encoding, just to experiment (didn’t work), then made a new Unicode-encoded file, and the icons were restored. So, just be sure to click that wrench icon next to the download button on Fontello, scroll down to “Set Encoding,” and select Unicode, and that should fix it.

It would be great to be able to add a class to buttons so that we can take advantage of the fact that you already have PrettyPhoto integrated.

That way visitors can open iframes, videos, images etc. within a lightbox by clicking a button element.

Another solution would be to add some these options within the button edit area. For example:

Open link in lightbox? Yes/No

Width of lightbox: X (mainly for iframe)

Height of lightbox: X (mainly for iframe)

Thanks!

Ron