Upfront not loading editor on Dreamhost hosting account

I just installed the WPMU Dev dashboard plugin and Upfront/Fixer theme on a Dreamhost server but the Upfront edit page refuses to initiate.

This stems from a problem posted earlier where I tried to migrate a local development version of the site using All-in-one-Wp migration tool. The site migrated over just fine, as it usually does with the migration tool, but again the Upfront editor would not kick in - same thing it is doing now. The same spinning lines go on forever but nothing loads in.

any suggestions would be appreciated....

  • Michael Bissett

    Hey @Thomas Sarkisian, hope you're doing well today! :slight_smile:

    Just to be certain, does it only do this when you migrate a site over using this tool? If you were to create a fresh site on your hosting, and try using Upfront there, does it work properly then?

    While looking inside your site via the Support Access you granted, I did notice these two script errors:

    underscore.min.js:1 - Uncaught SyntaxError: Unexpected token >
    
    underscore.min.js:1 - Uncaught SyntaxError: Invalid regular expression: missing /

    One cause of this can be Varnish caching, could you try disabling that (or ask your host to do that), and seeing if that helps at all?

    Please advise,
    Michael

  • Thomas Sarkisian

    Hi Michael,
    I ditched the migrated version of the site because it too did not work for the same reason, I reverted it back to the original site. I then installed WPMU Dev Dashboard as a plugin then Upfront via the WPMU dashboard on the old site, but still can not enter the Upfront editor.

    Can you give me more details about 'Varnish' caching ? What exactly am I supposed to request from Dreamhost and how might that effect other sites on the server account?

    Cheers....

  • Thomas Sarkisian

    Recent reply from Dreamhost:

    I'm sorry that you are encountering these issues. I was able to login
    this time with the new login credentials you supplied me with. I was not
    able to see that the slowing you were seeing. I ran a few tests and found
    that sites that are running under your user "herzoox" are occasionally
    hitting our shared server's memory limits. This is why your site is
    seemingly slow, and the 500 errors are directly related as well. Here is
    an excerpt from the log kept by our Process Watcher, the daemon that is
    killing your troublesome php5.cgi processes:

    Thu Apr 23 08:58:17 2015 procwatch3 INFO: PID 31364 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Thu Apr 23 08:58:17 2015 procwatch3 INFO: PID 31235 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Thu Apr 23 09:05:03 2015 procwatch3 INFO: PID 31363 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Thu Apr 23 09:05:03 2015 procwatch3 INFO: PID 31234 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Fri Apr 24 03:14:30 2015 procwatch3 INFO: PID 26224 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Fri Apr 24 03:14:30 2015 procwatch3 INFO: PID 21817 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Fri Apr 24 03:17:03 2015 procwatch3 INFO: PID 14611 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Fri Apr 24 03:19:25 2015 procwatch3 INFO: PID 15364 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Fri Apr 24 03:19:25 2015 procwatch3 INFO: PID 15090 (php53.cgi)
    herzoox:pg881900 : killed for uid ram
    Fri Apr 24 03:22:58 2015 procwatch3 INFO: PID 15518 (php53.cgi)
    herzoox:pg881900 : killed for uid ram

    Procwatch is a daemon that runs constantly on shared servers to monitor
    the usage of RAM/CPU and execution time so that no single user can use an
    inappropriately high percentage of the shared resources and impact the
    overall health of the server or the server's ability to serve all users'
    pages.

    Now, it's important to get these errors fixed to keep your sites running
    with optimum speed, as well as keep our servers happy. Unfortunately it
    can often be a bit of a trial-and-error procedure, but I will provide as
    much information as I can to aide you in this process.

    Firstly, it should be noted that any sites running under your user can
    contribute to the problems you are encountering. For example, if site A
    is running processes that are taking up 85% of your individual limit, and
    site B tries to run a concurrent process that takes up 20% of the memory
    cap, site B will have it's process killed since it is the one that took
    you above your limits, even though site A's script is the obvious memory
    hog... For this reason, it's important to keep all of your user's sites
    optimized and running smoothly.
    -------------------------------------------------------------------------------------------------------
    It looks like they are basically saying that the problem is the theme!

  • Michael Bissett

    Hey @Thomas Sarkisian,

    After talking about this with one of my colleagues here, it's sounds like we've run into an issue mentioned in another thread that came up recently. We'll want to have a deeper look at things here, could you please send in the following via our contact form:

    - Mark to my attention, the subject line should contain only: ATTN: Michael Bissett
    - Do not include anything else in the subject line, doing so may delay our response due to how email filtering works.
    - Link back to this thread
    - Include WordPress admin access details (login address, username & password)
    - Include FTP log-in details (hostname, username & password)
    - Include any relevant URLs for your site

    On the contact form (linked to below), please select "I have a different question", this ensures it comes through and gets assigned to me.

    https://premium.wpmudev.org/contact/

    Thanks a bunch! :slight_smile:

    Kind Regards,
    Michael

  • Thomas Sarkisian

    Dear Michael,
    Ok great thank you so much! I confirm that it is now possible to enter the UpFront edit mode.

    So, next...transfer of my local development version to the server either via Snapshot or All-in-One-WP migration plugin - I assume doing that will overwrite the patch?

    Also, I have another UpFront site that I need to migrate to a new Dreamhost account. What do I need to do to make that happen?

    Thanks for all the help!
    Cheers,
    Thomas

  • Michael Bissett

    Hey @Thomas Sarkisian,

    You can make a copy the /upfront folder that's presently on your hosting, and then once you've restored your snapshot/backup from your local site, you can just replace the version of Upfront from the local site with the patched copy.

    You could also import the patched copy of Upfront to your new site as well. I was going to create a .zip archive for you here, and attach it to the thread, but the access I have presently doesn't allow for that (though if I had the cPanel credentials for your site, that could be easily done).

    Hope this helps! :slight_smile:

    Kind Regards,
    Michael

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.