Profile for User: Kriesi

Totally understand the issue but most people want to translate both front and backend. Those are obviously people who are simply using enfold with the one or two languages they know so i see your problem when it comes to managing 9 languages.

I think the easiest way might be to trick wordpress into thinking that there is no translation file when in backend. You might want to try the following:

If you are using a child theme copy the following function to your child themes function.php file, otherwise you need to edit it directly in your themes function.php file at line 241:

if(!function_exists('avia_lang_setup'))
{
	add_action('after_setup_theme', 'avia_lang_setup');
	function avia_lang_setup()
	{
		if(!is_admin())
		{
			$lang = apply_filters('ava_theme_textdomain_path', get_template_directory()  . '/lang');
			load_theme_textdomain('avia_framework', $lang);
		}
	}
}

This change in the function (I have added the is_admin() clause) will tell wordpress to find the translation file when in your frontend but not when you are in the admin area. Let me know if this helps

great, let us hear if you got any follow up infos. If its indeed a problem with the theme and the server we would love to make it work but I am not sure what exactly we can do if it works for almost every other hosting environment :)

Hey!

We are using a custom frontpage with the following shortcodes

[bbp-forum-index]

[bbp-topic-index]

Regards,
Kriesi

• This reply was modified 10 years, 2 months ago by Kriesi.

Hey!
Yes, we are going to remove some of the deep integration with the plugin since it seems that is causing more problems than it helps…
Will see if thats going to fix the issue :)
Cheers!
Kriesi

Hey!

Would recommend to do that then and also check if this happens with the default theme

Cheers!
Kriesi

Hey!
thanks. this is a known issue with the latest versions of firefox and IE. A bugfix will be released within the next 24 hours ;)
Best regards,
Kriesi

k. Update will arrive later today or early tomorrow ;)

Hi momon!

Its a framework post type that is used to store images. With the new gallery that wordpress added in version 3.5 it became less relevant but previously it made sense to upload images to such a post because the gallery option grouped images uploaded to a post. So for example if you uploaded 3 versions of your logo it would group them and it would be easier to select them if you change the logo.

Best regards,
Kriesi

Hey!
If I am not mistaken this has changed with the latest wordpress update. The text field now expands automatically if a lot of content is inside. I am afraid there is currently not much we can do about this behavior….
Regards,
Kriesi

k ;)

If you want to, I can try to upload wordpress and the theme again but I am not sure if this is going to help. As I said, this does not appear to be an issue related to the theme since I cant upload images even if switching to the default theme…

A “enfold.css” file is not in the upload package. The file is generated once you save the theme options and then usually saved in the uploads folder, since this is the only folder that should be writeable for wordpress by default. For a unknown reason that upload folder is not writeable for any theme. Truth to be told, I cant really imagine why but my best guess is that it has something to do with the permissions that the php-user has in those folders…

Thanks!

Just checked it again and at this point I am pretty sure that this is nothing related to enfold. I checked your ftp server and every operation that creates a file fails.

2 examples:
Once you save the enfold options WordPress creates a stylesheet in the uploads folder. But on your server that does not work. So I switched to the WordPress default theme and tried to upload an image, which also fails. The database entry is set in both cases and there are no visible errors (which is odd) but neither the stylesheet nor the uploaded image are created by WordPress, no matter the theme.

Permissions look fine for me, but since I am not really a server-guru there might be other settings that prevent WordPress from creating files on your server. Do you have any idea why this might happen? It seems it has worked at some point in the past, since I can find a few images in the uploads folder, as well as an Avada stylesheet…

Hey!

I have googled the term “wordpress 502 Bad Gateway” and what I get are a lot of different threads with that problem (not related to enfold, most of the time other themes or plugins) and a lot of those threads mention wpengine so I am not really sure if they are running some special kind of servers. The error does not happen for our other 40.000 enfold customers and as I said above is caused by generic wordpress functions that are not even theme specific, so I am having a hard time helping here, with no way to reproduce the issue :/

From what I gathered in some of those threads mentioned above, its maybe because there are not enough resources available for the database. Not sure if there is something you can change in your wpengine dashboard to increase that?

Best regards,
Kriesi

• This reply was modified 10 years, 3 months ago by Kriesi.

Hey!

The thing is: if this was a common issue we would have thousands of users complaining about it and I would also have noticed it in my own backend. Since thats not the case, and since I cant reproduce it in any way on my own installation there has to be something on your installation that is unique. Either a plugin, a server settings, a ftp problem etc, so we will check all of that :)

Thanks for the login credentials, as said above I would be glad if you could drop me the FTP credentials as well since right now it sounds like that might be the problem…

Cheers!
Kriesi

@jelito: it seems that a crucial file is missing on your installation. I get the following error:

POST http://perfil.com.uy/nuevo/wp-admin/admin-ajax.php 404 (Not Found)

Maybe there was a problem when updating to the latest version of wordpress since this is not a theme file but a wordpress core file. Would recommend to check if the file exists and maybe try to re-install your latest wordpress version.

@khaled:

Its quite easy:
If you update to the latest version and it still does not work I can check the backend for error messages and see what it says and fix it, but if you dont update I always get the error message that was already fixed.
So either you update to the latest version and we investigate from that point or you dont update and we close this thread. We can’t help if you are not running the latest version of both the theme and WordPress.