Sitejet support
When will a qualified customer support for sitejet product be available?
my sitejet instance has many issues unresolved for a week now and no one can help, as the cpanel support people are not knowledgeable/trained around what sitejet is and how it works. They provide useless suggestions and recommendations, usually do not understand the nature of the problem at all. can't distinguish between XML and HTML and don't understand sitejet functionality etc. Absolute useless support to be honest.
-
Hey there! I'm sorry to hear about issues with the support. Have you submitted a ticket to our team? If so, we can always escalate the ticket to Sitejet if we aren't able to resolve the problem.
If you already have a ticket open with us, can you post that number here so I can check it out?
0 -
95259120,
95259200,
952593930 -
Thanks for that. In ticket 95259393 we weren't able to reproduce the issue.
The other two tickets are still being actively worked on by our L2 and L3 teams. I did leave a note on each of those tickets about this Forums post as well, but you'll be hearing from us soon with more details.
0 -
Ticket 95259393 is about invalid file paths. To reproduce this your developers just need to look at the publishing log files. The last response to that ticket is from a person who doesn't understand sitejet functionality. An expert would have recognised where these invalid paths are coming from (they are in some XML files that are used in publishing) suggesting me to check the paths in html code. 🤦🏻 I never heard about those XML files existence and never created those paths.
0 -
cPRex, agents who work on 95259393 ticket do not understand Sitejet basics. You don't need to do anything to reproduce the issues. Observing the publishing log file should be sufficient, it has all the information needed - https://backup.thai-remedial.com.au/publish_2024-05-15T12:41:35.log (this is most recent, one of many log files that have the same repeating issues)
You can't suggest user to manually edit xml file that belongs to the template (is created and managed by sitejet process)
https://2f5b83-9f7be.preview.sitehub.io/spa-template-news/230888031.xml
- this one is part of the sitejet template, was created by the sitejet process and stored on sitejet's sitehub.io server. Manual edit of that xml file on web server won't make any difference as the original (source) file stored in will remain the same and will always overwrite the server file on publishing.
Do you have a qualified Sitejet expert in the team who can look into the issue?
I can see you are promoting Sitejet on cpanel, on this forum (banner at the top) - system that obviously has lots of bugs and needs a qualified user support.
It can't be that a non-user (with minimal sitejet experience) helping a user. That is not helpful at all, unfortunately :(
The sitejet is a great CMS (very similar to Webflow). Having it integrated into cpanel as a free add-on is a very cool feature for web developers. Its popularity along with cpanel can grow a lot, but needs a qualified user support. Right now, it creates a negative impression especially for a first-time user, with lack of qualified support.
1 -
95259393 has been closed for a bit now, but 95259202 is the ticket currently being handled by Brian. Brian is an excellent technician but it seems you haven't provided the information he's looking for in the ticket as we still aren't able to reproduce your exact issue.
If there is an issue within the ticket please ask for a supervisor as I'm not able to do anything with that ticket through the Forums, but from what I'm seeing the ticket is going well.
0 -
95259202 is the one where conversation on the issue(s) is going on. 95259393 was incorrectly closed as unresolved.
This needs a real sitejet expert attention and cold be resolved in no time (or raised with developers if this is a system bug).1 -
Yep, looks like if SiteJet is going to be a success it needs some development and also rock solid support who are going to be absolutely relentless in fixing every issue. Without that, it won't end well.
I had a play with it today to see what it's like. Honestly it needs to be way easier than it is if we are going to sell it to some small business owner who just wants to choose a template, fill out some fields and type some text and have a website. I was hoping it would be more appropriate than Wordpress for this, but honestly at the moment I think I can give some instructions to someone to setup Wordpress and it will be easier than Sitejet right now.
I REALLY hope they improve it because it could be a transformation for cPanel and web hosts like us. If we as the web host are going to be in the middle of a fight with a customer issue, and it's not even going to be all the code on our system, that's completely unacceptable for us.
If within an hour or so of playing and just doing a completely basic site with no features, I was able to encounter an issue that completely prevented me from publishing the site, it's not a good start. If I was a customer I would have already been calling for support.1 -
I agree with the above posters' comments 1,000%.
I am a GoDaddy customer with a Virtual Private Server (AlmaLinux 8) host.
I consistently experience the following (non-starter) error from cPanel when attempting to launch SiteJet Builder from cPanel:
Oops!
Something went wrong when initializing your Sitejet account.***
Error
The request failed. (Error ID: u5vfmb) Ask your hosting provider to research this error in cPanel & WHM’s main error log.*NOBODY* is available (or willing) to offer any SiteJet technical support (to ANY degree).
Frustratingly, I am caught in a loop: GoDaddy instructs me to consult SiteJet… who refers me to cPanel… who insists I must work with GoDaddy.
A desktop app would be (much) preferred (at least in my case).
0 -
GOOD NEWS: I was able to solve my SiteJet Builder launch/run problem simply by upgrading to and specifying PHP version 8.3.
I hope this fix proves to be permanent - and that the next cPanel integration of SiteJet Builder does not break everything.
1
Please sign in to leave a comment.
Comments
10 comments