Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • Thread Starter Christoph Letmaier

    (@chrisiwien)

    Thanks for your answer.

    I looked around on my local installation (xampp), and find in the Apache error log this line: “child process xxx exited with status 3221225477” – that error seems to be related to running out of ressources.

    I rised the value of “ThreadsPerChild” from 150 to 550 in apache/conf/extra/httpd-mpm.conf, and the value of “ThreadStackSize” to 8388608 (Section “<IfModule mpm_winnt_module>”) and restarted the Apache server.

    Locally that helped, now WordPress 6.5 and WooCommerce 8.7 are working, as far as I see.

    The problem occur on Windows Machines with Apache Webserver, i use xampp locally, online Windows Server 2019 and 2022 with Apache for Windows, installed manually. I will try this solution later on the online servers.

    Perhaps you place a note on the WooCommerce server requirement page which address this (Windows/Apache related?) problem.

    If further troubles arise, i will contact WooCommerce-Support as you proposed.

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    @seank123: it didn’t say it works on the local server. On the local server I run the downgraded configuration that works.

    The problem appeared suddenly, i have nothing changed, so i assume the problem has to do with very new versions of WordPress/WooCommerce and automatic update.

    Also, I run another live server with the exact same configuration, the problem occured there likewise and at the same time.

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    Thank you for your answer, it works this way.

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    Very well, but the user account has configured the option that the admin bar doesn’t show up on frontend, so your solution will not work in this case.

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    Thx for the answer!

    Further more, this behaviour of Gutenberg throw errors in the W3C validator (https://validator.w3.org/):
    Error: Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.)

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    @mostafas1990: Unfortunately I don’t have time for testing right now.

    @danipmd: from the WP Rocket support team I got this proposed debug workflow:

    1. On the Media tab, uncheck LazyLoad
    2. On the File Optimization tab, uncheck each option, one at a time.
    3. Each time you deactivate an option, check your site in a private/incognito browser window where you’re not logged in as a WordPress user.
    4. Reload the page a couple of times to make sure it’s cached. When the issue resolves, you know it was caused by the last option you disabled.
    5. Once you know the option that causes it, consult this guide for possible fixes:http://docs.wp-rocket.me/article/19-resolving-issues-with-file-optimization

    I did not try that, maybe it helps you.

    This seems to be a Gutenberg bug. I am facing the same problem from time to time.

    “Workaround”: log out and close the browser window. Be sure to check that no other browser instances are running (Windows: via the task manager).

    Restart the browser, re-login and the overtype mode is disabled again.

    Since Gutenberg seems to be a heavy JavaScript framework it doesn’t like if your are too quick with typing an clicking… πŸ™‚

    There is obviously some sort of race condition in the code.

    Keep in mind if your page/post has many blocks Gutenberg gets slower and slower, this could be also causing the hassle.

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    Update: in a recent try it worked. Perhaps the problem is, in my case, that I disabled wp_cron in wp_config.php (for performance reasons) and defined the execution of wp_cron.php via my server settings. So I have to wait for cache updates until wp_cron.php is executed again…

    Strange, WP Super Cache works only when wp_cron.php is called. Is there a reason for this behaviour?

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    Hello Jason!

    Hm, best would be adding just other textares below, one for each available language in WPML. So, at the moment I don’t have the code ready, but i’m shure it is easy:

    1. to get all languages defined in WPML
    2. render a textarea for each language
    3. store the content of the textareas as an (best associative) array in the wp database
    4. fetching the appropriate array index if the PHP condition (example for German) if($_GET[lang] == "de" || strstr($_SERVER['REQUEST_URI'], '/de/')) is given.

    I’m not sure what I will do, I need it soon. Building an add-on for slimstat would be the best way. Another – not very elegant – way is to put the text for all languages in the single textarea and wrap each language in something like <div "optouttext-[lang]" style="display: none;">, then showing only the appropriate <div> via a JavaScript function which filters the URL, if it is possible.

    Slimstat is an alternative to Google Analytics and many people are looking for such an alternative. So, the future is in Europe already there, and, as you know, there is not only one language spoken in Europe…;-).

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    Hello Jason,

    hm, then please tell me how to add other languages for the opt-out message.

    In the available field “Opt-out message” there is only a html input textarea. Since I’m using WPML i need PHP to add a string for the String Translation Tool or an input textarea for each language.

    I want “This website stores cookies on you computer” in english and in German (if someone opens the site from Austria, Germany or Switzerland) “Diese Website speichert Cookies auf Ihrem Computer.”

    Also in english the buttens “Accept” and “Deny”, in German “Annehmen” and “Ablehnen”.

    This is not possible with HTML only, as far as I know.

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    Hi Alex! I’ve already posted some messages on the appropriate page: https://github.com/GM-Alex/user-access-manager/issues/80

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    I’ve discovered that the SiteOrigin PageBuilder doesn’t write the content into the page conent are, it uses user defined field (WP table postmeta, meta-key “panel_data”.

    I think that is the problem. UAM doesn’T process the whole page (with the user defined fields) but only the content area.

    Thread Starter Christoph Letmaier

    (@chrisiwien)

    This is not a solution. Your suggested google search is leading only to a xampp related solution. However, the problem seems not to be xampp related since static pages are loading well as mentioned in my orginial post.

    You’re welcome.

    No, you don’t need to install another theme – since you can use only one theme at once.

    When you create a new cms-page in the right column you find a box labels “Attributes”. There you can select between two templates, one should be labeled like “Standardtemplate” and the other “Template”. I’m not completely sure about the english names, because I work with a german version of wordpress.

    If you select “Template” you can build the site with the standard features: just a title-box and a box with the WYSIWYG-Editor. Sidebars are visible with this simple template.

    However if you select “Standardtemplate” the sitebuilder-boxes appears (where can add banners eg.), in this case, the sidebar remains hidden, regardless of your theme-settings.

    If you want sidebars with the sitebuilder-template active you have to go into the code an change something, but that will be quite an effort…

    Perhaps you have more options in the commercial version of MAKE…?!

Viewing 15 replies - 1 through 15 (of 16 total)