Skip to main content

Sitejet staging directory?

Chris Matthews

Sitejet is a great addition to cpanel, well done!

It does look a little difficult though for clients who have an existing website to have to create a new domain or subdomain, clear their / directory then move files over. Is there no way to make this a little easier? A staging directory perhaps?

Comments

19 comments

Date Votes
  • Ryan Smith

    I was wondering about this issue as well and was told they can make a staging subdomain, and then manually copy those files over to their production site, but they'll have to always edit on the staging site and manually copy files after, which isn't very user friendly at all.

    A proper staging/production system would be welcomed, but I think what would be even easier is if they could just start building in SiteJet on any domain, and then it does these checks before publishing. So it'll just block them from publishing until they delete their old website. This is how most other website builders we've used have functioned.

    1
  • cPRex Jurassic Moderator

    Sitejet also has the "publish" feature, so any changes you make aren't live until you click the publish button, leaving your existing site/files intact.

    0
  • Ryan Smith

    You can't start using Sitejet in cPanel if there are any files in the domain's folder, it displays the following message:

    You cannot create a Sitejet website currently. For more information, read our documentation.

    It would be great if the could actually start using it on a domain with an existing site but that's currently not possible.

    1
  • Chris Matthews

    You also can't create a site using Sitejet if you have any files ( and they all do ) in your root directory.

    This procedure is too complicated for a lot of people

    Shared document root

    You cannot use a shared document root directory with Sitejet. To resolve this issue, do one of the following:

    1. Use Main domain.
    2. Create a new domain.
    3. Delete the second dependent domain.

    You can now create a Sitejet website for that domain.

    Document root directory contains files

    If your document root directory contains files, you cannot publish a website with Sitejet. To resolve this issue, you must delete the files in this folder.

    1
  • cPRex Jurassic Moderator

    Well that defeats the point of the delayed publishing option then.  I'll bring this up with the team!

    0
  • Chris Matthews

    @cPRex, Thanks.

    Were going to hold off mailing our clients about Sitejet because we feel our support ticket system will fill up with confused clients!

    1
  • cPRex Jurassic Moderator

    Update - we have an internal case open to see if we can get a staging area of some sort created.  I'll be sure to update this thread if I hear more details!

    1
  • MICHAEL ST-ONGE

    Hi,

    I don't know if this relates to me but I have created a subdomain on an active Cpanel account to use Sitejet Sitebuilder. I asked that the subdomain points to a subfolder such as */publich_html/subdomain .

    I created a simple Sitejet page (single page) and tried to publish it but it doens't want to publish. Here's what I get:

    [2024-01-22 20:43:10 -0500] info [uapi] [0 s] Starting sync for madalena..cliniquechurchill..com at 1705974190..

    [2024-01-22 20:43:10 -0500] info [uapi] [0 s] Download sitemap xml:https://222f4e-714db..preview..sitehub..io/sitemap..xml

    [2024-01-22 20:43:11 -0500] info [uapi] [1 s] fetchUrlsFromSitemap etag mismatch found.. current etag : 8456defba5d3eb0a201aef17bfa06369 expected_etag : cb9e0c603735b534e5cef076bf6f4d02

    [2024-01-22 20:43:16 -0500] info [uapi] [6 s] Download sitemap xml:https://222f4e-714db..preview..sitehub..io/sitemap..xml

    If this topic isn't related to my error, than please excuse me as I'll open a new thread for it.

    Thanks and have a great day!

    Michael

    0
  • cPRex Jurassic Moderator

    MICHAEL ST-ONGE - it's not related to this topic, but it's still fine to discuss.

    I believe your issue is related to internal case DUCK-9904 - "Sitejet publish fails when executing with just one page"

    This will get resolved soon, but in the mean time you can just add another page and it should work well for you.

    0
  • MICHAEL ST-ONGE

    Fantastic, that did it! Thanks for your help

    0
  • cPRex Jurassic Moderator

    I'm glad that's all it was!

    0
  • Unnamed User

    Any update on the staging directory request?

    1
  • cPRex Jurassic Moderator

    The specific case for the staging directory is DOC-20190 and DUCK-10345.  It's still being worked on but I really hope this one goes live soon!

    0
  • Unnamed User

    I am playing with sitejet for the first time and I am having the single page publication issue DUCK-9904 that is mentioned here.  How do I check the sitejet version?

    1
  • cPRex Jurassic Moderator

    DUCK-9904 has been resolved since January, which you can see in the change log here:

    https://docs.cpanel.net/changelogs/sitejet-builder-change-log/

    You can check the Sitejet version by checking the RPM that is installed on your machine.  For example, my personal server shows this right now:

    rpm -qa | grep -i sitejet
    cpanel-sitejet-plugin-1.4.1-2.3.1.cpanel.noarch

    so that would be 1.4.1-2 from the change log.

    0
  • Unnamed User

    Ok interesting.  With an up to date cpanel installation, would you normally expect sitejet to get updated with the normal cp update process?  Ours was very old but the server looks to be updating ok.

    0
  • cPRex Jurassic Moderator

    Yes, I would expect that to update automatically.  Are you on an older version?

    0
  • Unnamed User

    No, the server looks fully up to date, however we ran dnf to update that package and it updated. Have not tested it out yet but I assume it’s fixed now. We will look further into why it wasn’t updated automatically.

    0
  • cPRex Jurassic Moderator

    Let me know what you find!

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post