If you have troubles since the update to WordPress 4.5 please read this post before opening a new thread.
February 24, 2014 at 12:34 am #228261
I have searched the forum up and down, I have tried different solutions, and nothing seems to work.
Sometimes I cant use the text block of the avia layout builder.
I see the text that I have previously written, but when I click it it says “Click here to add your own text”
Will you please help me with this. It is not consistent. It has happend once before, and then just resolved by itself. Maybe an update on some part?
It is not a problem on each page, so I am really scratching my head over this. When I try creating new version of the page, I get to edit text, but not upload an image. .. Please help. I was supposed to launch this page today with the client.February 24, 2014 at 3:23 am #228300
Typically this is an issue with a low memory threshold for WordPress. Try increasing your php memory limit to 96m+ and that should prevent it from happening.
DevinFebruary 24, 2014 at 3:44 am #228313
Please give us a link to the page. Increase the wordpress php memory limit. Refer to this link.
IsmaelFebruary 24, 2014 at 10:23 am #228398
My memory limit is already set to 128. That is the max limit according to my host ( bluehost)
I just did the update also of theme files, no change.February 24, 2014 at 10:23 am #228399
Thank you for looking into this with me! :)
It feels like there is going to be a solution when I am not alone with it!February 24, 2014 at 10:40 am #228407February 24, 2014 at 10:51 pm #228704February 25, 2014 at 12:46 am #228754
As a general fyi our queue system goes by oldest posted item within a topic to newest so each time you self bump it actually pushes you further back in our queue.
Looking at your installed plugins it might be an issue in getting high spikes in memory usage where the page data has an issue saving. If it isn’t happening consistently as it doesn’t seem to be that is my best guess on why it would happen sometimes but not others.
You could also try disabling the Tiny MCE plugin and see if it helps though it didn’t show any errors when looking and testing out things just now.February 25, 2014 at 1:09 am #228761
Hi Devin! Thanks for the info! :) I will not bump myself again! :p
I tried everything I could think of and as suggested. Nothing worked. It almost seems to me there was a bug “living” in the pages affected. I deleted the pages and recreated them. All works fine on the “new versions”
What seems to be te problem now, which I could do earlier, is that I cant copy content between languages.
I just recreated it for the sake of one portfolio item,but it will become bothersome if I get o dozen to put in!February 26, 2014 at 3:21 am #229360
I’m pretty sure that the pages aren’t able to be copied between layers when using the ALB. They need to be manually re-created or copied over using the debug field since WPML doesn’t recognize the setting where the layouts are stored on each page.February 26, 2014 at 9:49 am #229477
Well, I am pretty sure that’ts what I did with the previos 20 items and on 2 additional languages!February 27, 2014 at 6:17 pm #230177February 28, 2014 at 10:13 am #230519February 28, 2014 at 10:56 am #230535
Afaik you can copy/duplicate the content easily. Use the “Duplicate button” and then (when the translated entry was created) click the “Translate Independently” button to translate the content. Some layout elements (i.e. the portfolio grid, post slider, gallery or the blog element) require a separate configuration for each language because the ids of the categories and of the translated post/attachment entries vary from language to language. Static elements (like textblocks) do not require a separate configuration but obviously it’s necessary if you want to translate the static text. I created a short video which demonstrates the translation process and which also shows you that the categories may vary from language to language (i.e. if not all categories are translated, have a different name, etc.): http://www.screenr.com/CBBN
You must be logged in to reply to this topic.