Forum Replies Created
-
Posts
-
Thanks, Rikard. Actually it was the server which responded quick but seemed to have some problems building the database-queries.
So have been right.
Thanks!
/closedHi Rikard, thanks for your quick reply!
As I am sure the server is quick – isn’t it possible that the waiting time is induced by the CMS/theme constructing the html-code to be delivered?Thanks, bnetz
Hi Nikko,
please have a look at the screenshot (attached in private area).
I expected the demo-import to look exactly like the demo I get online ( http://kriesi.at/themes/enfold-2017/ ), so I am confused that it looks different.Hi Nikko,
thanks, I tried this, but this changed nothing. I did “import parent settings” also.
When you look at my site at the footer you see the differences immediately.
Hi Rikard,
I’m not sure if I understand what you mean – I tried copying the css (see link to css in private area attached) into the Quick-CSS-field; some things get fixed, some not. I guess that the problematic elements are located in different css-files.
Hi Rikard,
this seems to work. So let’s close this thread, thanks for your help all!
I want to add that the import of the enfold-demo is really, really annoying – a lot of people seem to have similar problems; I myself am no beginner to webdevelopment, installing the demo has taken 18 posts. And there still is no definite solution – for some reason the import seems to work sometimes and sometimes not (100% same system/configuration, import first didn’t work, then it did).
So this situation is not professional, and I think there should be some solution, at least in form of an extensive tutorial.Hi Victoria,
I just had another try with exactly the same settings, and it now seems to have worked. I am not sure if it actually HAS worked, because the top-menu in the frontend seems not to be displayed correctly. Perhaps you could have a quick look if there just went something wrong in the settings or if the demo-import still has problems? Login-data in private area attached. Thanks!Hi Victoria,
thanks, I set all the values accordingly (post_max_size = 64, upload_max_filesize = 64), the server accepted those values (as you can see with phpinfo()), but I still get the same error.Thanks for further help :-)
Hi Victoria,
I tried this 2x with an absolutely fresh wp-install and it did not change anything.
Do you have other ideas? I attach a link to the phpinfo()Thanks
Hi Victoria, thanks for the links.
The first one suggests to install without subdomain (xy.com instead of http://www.xy.com). As I am developing on a subdomain this is no solution.
The second one contains informations about the max_execution_time and the memory_limit, but here everything seems to be ok with me (see my php.ini and the phpinfo()-link attached to my last post.
The third one tells me how to adjust memory_limit and max_execution_time. As you can see in my phpinfo() the memory_limit is 128M and the max_execution_time is 300.So the links still provided no solution for my problem. I have ftp- and ssh-access to my webspace and to the database also via phpmyadmin. So perhaps it actually could be a solution to import the demo manually? Unfortunately the way I tried the xml-import (described above in this post ) did not work either with the same error-message in the WP-backend.
Is there any help for me?
Login-data to backend, ftp, mysql are to be found above in this post.Hi Victoria,
it was 5.56, now I tried with 7.0.6 – I attach a link to the phpinfo(), perhaps you find something useful there.
The error_log I defined in the php.ini registers no errors when I try the import and get the error message in the WP-backend. Also I get no php-errors shown on the website (though I tried to activate them via display_errors = On in the php.ini). I attach also the contents of the php.ini, perhaps there is any misconfiguration?!
Thanks!
Hi Basilis,
I definitely have 128MB memory_limit (phpinfo also does show this) and I re-installed WP (4.8.) again from scratch. The xml-import produced the errors described above; I reset WP fully and tried again the import (via Enfold -> Demo Import) and got the errors described above.
I should mention that I am not a WP pro but that I am running several smaller WP-sites. So I am a little bit annoyed having so much stress with the demo-import and further on I would appreciate help very much because I am keen on using enfold. Thanks.
Hi John,
I tried to import them with the WP-standard-xml-importer (under Tools -> import); I imported the file which I found in the path you mentioned /enfold2017.xml , but I get a bunch of errors like
WordPress importieren
Import des Beitrags-Schlagwort fehlgeschlagen
Import des Beitrags-Schlagwort fehlgeschlagen
Import des Beitrags-Schlagwort fehlgeschlagen
Import des Beitrags-Schlagwort fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagen
Import von fehlgeschlagenDo you have any idea how to complete the import without errors?
Thanks
Hi John,
I can use 128MB memory limit with our recent packet. I could upgrade to get 256 MB, but this would be about 10USD/month. I would do it if I could be sure that this is the reason.
So you definitely say that 256MB memory-limit is required and that 128MB is most probably the reason why the import does not work?btw it would be nice to have somewhere a tutorial how to import the demos manually.
