Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter hwcelli

    (@hwcelli)

    this helped me, set in custom css section of our used template

    .job_listings ul.meta .date { display:none !important; }

    Thread Starter hwcelli

    (@hwcelli)

    @mike, please read (from wpengine):

    Hi again Marcel,
    After much testing, I found that the core of the issue is that the WordPress rewrites for /job/ are missing when the site is broken.
    In addition to being able to fix things by hitting Save Changes in wp-admin -> Job Listings -> Settings, changing the theme to something else then back to Avada also fixes the issue, because both of those actions regenerate WordPress’ rewrites.
    Unfortunately I haven’t been able to find why those rewrites are being dropped however. I thought it might be from our database cleanup script that runs daily at 2am UTC, which clears out extremely large database rows, but I don’t think that’s the cause because A) It would wipe out all rewrites, not just the ones for /job/ and B) the timeframes of increased 404s in the logs don’t line up with when our script runs.
    If possible, I suggest reaching out to the developer of the plugin and see if they’ve ever seen anything like this before – Perhaps they can offer some insight into why it’s happening, or suggest something else we can check on our end here.
    I hope this information is helpful Marcel, feel free to let us know if there’s anything else we can do.
    Best regards,

    What do you think?
    Marcel

    Thread Starter hwcelli

    (@hwcelli)

    Hi Mike

    no the whole morning they was up and down….all the time….

    got this from WPengine:
    Hey Marcel,
    Thanks for keeping us updated on this. I know it must be frustrating to have the site randomly displaying error messages like this. I apologize for the inconvenience.
    I was able to replicate the error again, and in doing so I attempted to track it with some additional logging that I’ve enabled on the install. Unfortunately, the logs didn’t display any thing of assistance to us at this point.
    There has been a known issue with an update we did to our object caching system recently, and I thought that might be part of the issue, but even after applying our patch for this issue, the error persisted. However it is possible that applying the patch will prevent the issue from occurring again.
    Following this, I applied the fix as you suggested in your original request, so that the page does not continue to deliver 404 errors.
    I’ve left the debug log enabled at this time so that if the issue does occur again we can catch it in the act. However, as this seems to be a difficult issue to track down, I’m going to escalate this ticket in a pending status to our senior technicians.
    This means that we’re going to see if the issue comes up again, and if it does, your next reply to the ticket will open the ticket for our senior techs to investigate.
    If you do see the issue again, please let us know and we’ll continue the investigation. Thank you for your patience through this process!

    @mike, since they have done this, means 2,15h, all pages have no downtime, hopefully this was the trick 🙂

    Regards
    Marcel

    Thread Starter hwcelli

    (@hwcelli)

    Wpengine disabled Cache function on folders /job/ and /jobs/

    i have deactivated all additional stuff in .htaccess ……

    this morning i had 500 emails in my Mailbox…. no the pages are up for some minutes and the down for some and so on….. automatically….

    its getting more bad as more we try….

    Marcel

    Thread Starter hwcelli

    (@hwcelli)

    Mike, on the staging area, where is no Caching function active, i never had an interuption of Service since last thursday night till yet.

    i took out the part within htaccess for the Caching on PROD, which helped a lot….it was 20 times longer reachable…..it`s still stuggeling but not that often….as before

    i copied the whole PROD to a DEV area and Setup now again 3 links which i check every 5 min with uptime Robot…..we will see what happens there…. it has the std. htaccess without any plugis etc

    http://dev3alfapeople.wpengine.com/jobs/

    Regards Marcel

    Thread Starter hwcelli

    (@hwcelli)

    Hi Mike

    we have a staging area where we can do tests:
    http://alfapeople.staging.wpengine.com/jobs/

    ive added there also 2 jobs and they dont have this 404 problem, all plugins and theme etc is the same as on our PROD page…

    exept that there is no cache function working (as wpengine.com told us: There is no server side caching in place on staging sites)

    on PROD we have this part in htaccess running:
    Header unset Pragma
    FileETag None
    Header unset ETag

    ## EXPIRES CACHING ##
    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType image/jpg “access 1 year”
    ExpiresByType image/jpeg “access 1 year”
    ExpiresByType image/gif “access 1 year”
    ExpiresByType image/png “access 1 year”
    ExpiresByType text/css “access 1 month”
    ExpiresByType text/html “access 1 month”
    ExpiresByType application/pdf “access 1 month”
    ExpiresByType text/x-javascript “access 1 month”
    ExpiresByType application/x-shockwave-flash “access 1 month”
    ExpiresByType image/x-icon “access 1 year”
    ExpiresDefault “access 1 month”
    </IfModule>
    ## EXPIRES CACHING ##

    ##############################################
    # COMPRESSION #
    ##############################################
    <FilesMatch “\\.(js|css|html|htm|php|xml)$”>
    SetOutputFilter DEFLATE
    </FilesMatch>

    <IfModule mod_gzip.c>
    mod_gzip_on Yes
    mod_gzip_dechunk Yes
    mod_gzip_item_include file \.(html?|txt|css|js|php|pl)$
    mod_gzip_item_include handler ^cgi-script$
    mod_gzip_item_include mime ^text/.*
    mod_gzip_item_include mime ^application/x-javascript.*
    mod_gzip_item_exclude mime ^image/.*
    mod_gzip_item_exclude rspheader ^Content-Encoding:.*gzip.*
    </IfModule>

    ## COMPRESSION ##

    php_value max_input_vars 3000

    Could here be the problem? because it has defenetly to do with caching…

    on PROD the 404 is also sometimes “healing” itselfs…without my interaction…this wasn`t in the beginning…..and also in the beginning all job details produced the 404…at the moment…it could be that just a few are producing the 404..

    Regards
    Marcel

    Thread Starter hwcelli

    (@hwcelli)

    Hi Scott

    we are using Avada (Themeforest)

    hmm ok i will search for how adding post types

    Regards
    Marcel

Viewing 7 replies - 1 through 7 (of 7 total)