Jump to content

Josh H.

Friends
  • Posts

    114
  • Joined

  • Last visited

3 Followers

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,666 profile views

Josh H.'s Achievements

  1. I've removed the most recent reply to this topic. If you know your way around the templating system and you decide one day you want to add a custom CSS rule to hide the upgrade notices, while this isn't something we can really stop you from doing, I will say rather bluntly that you would be very ill-advised to do so. Not only will this hide your current security update notice, it will cause all future notices to be hidden as well, regardless of how critical (or minor) they may be. Please also be well aware that we do not allow the posting of instructions on how to dismiss security notices, for reasons that really should be pretty obvious.
  2. I'm happy to hear you're enjoying the software Stormlily, and we appreciate you taking the time to share your feedback with us! I believe this is a subject that has come up at least a few times over recent months. As you've noticed, the forums here have actually only recently been re-organized so that it's more clearly displayed that they provide "Peer to Peer" support. Staff do not spend much time answering support topics here, so the support you get is indeed almost entirely community (i.e. peer) based. The reason being virtually all of our available resources are actively being consumed by support tickets and developmental issues (such as bug reports) at any given time. If you are ever experiencing a time sensitive issue and you need support from us, it would definitely be best to file a support ticket. In general though, I do understand where you are coming from, and I do think you have some fair points. However, for support related issues, this really is what our tickets system is for. I think the Peer to Peer support forums should mostly be considered something for issues that may not quite fit within our standard scope of support, or for issues that are minor in nature. One thing we are doing, however, is dedicating more resources to the community feedback forums (such as the one you're posting in right now), as these forums are especially important when it comes to company participation. I think that maybe sometime in the future when IPS4 has had plenty of time to mature and things have settled down, dedicating more staff resources to the peer support forums may be something worth revisiting.
  3. I understand your frustration. This was mostly just a case of bad timing. You were trying to access your client area right as the updates were being pushed out and some things were still in the process of being updated. It wasn't really something that warranted sending out a warning e-mail to all clients in the event that they happened to be trying to access their client area in that brief time window (and also happened to have actually read the e-mail prior to doing so). The glitches were very temporary and promptly addressed. Nonetheless, this was a relatively large change, so it's expected some hiccups may occur. If you experience any further issues, please let us know.
  4. Thank you for your feedback. As mentioned above, the new theme is a very recent change, so there are still a few kinks that need to be worked out. We definitely appreciate your support in helping us identify any of the remaining problem areas.
  5. Let's keep it civil guys. I've cleaned up the last several replies to the topic, there's no need for insults or other hostilities. This is indeed In Progress, meaning it is something that is being worked on. But there's never a shortage of work that needs to be done, so it's hard to provide an estimate on when some things will make it into the core. It's certainly fine to post your support in a suggestion topic even if it's already marked in progress. It does help demonstrate the level of demand for specific features, which can help when deciding what needs to be prioritized. (Don't take that as meaning it's okay to constantly bump your favorite suggestions asking "has this been done yet?", that kind of "demand" isn't what I'm talking about )
  6. There has been a lot of effort put into refactoring the documentation recently. Only a smaller portion of it is currently available, but you should see many significant improvements in that area over time. Pages is something that has particularly been getting a lot of attention, and should have some fairly extensive documentation available once all is said and done.
  7. Where are you seeing problems? Can you please provide an example URL that is not being processed correctly? I am not able to reproduce any issues using the example link provided earlier in this topic, http://en.wikipedia.org/wiki/Hart's_Rules
  8. If you need additional storage, you can always host your gallery images on Amazon S3. Then you can have the best of both worlds. You would need to upgrade to 4.x to take advantage of the Amazon S3 storage engine, however.
  9. Hi FZ, Thank you for providing us with your feedback. I'd like to address a few of your concerns directly. There have been a lot of significant improvements in regards to upgrading in 4.x. Notably, you no longer even have to manually download or upload anything to your server in order to perform the upgrades, the upgrader can automatically do all of this for you. So upgrading in 4.x essentially takes only a few minutes. So whenever you do make the upgrade to 4.x, this is something you can look forward to. I understand life being busy and not having a lot of time to dedicate to managing these things, however, that is why we provide our own Community in the Cloud hosting service. It's built for people who do not have the time or means to manage everything themselves. We can perform all upgrades for you automatically, so you don't really have to do anything. When you opt for self-hosting, you'll have to dedicate some of your time to maintaining your site and performing these upgrades, there's really not any way around it. When you're hosting with us, we can also do a lot more to provide you with immediate assistance, and issues like this seldom ever happen on Community in the Cloud anyways (as a large number of these tickets are actually server/hosting related issues and are not specific to the software). You're told to upgrade because these upgrades tend to resolve a wide array of issues, and we don't really have the resources to investigate individual issues on installations that are running out of date releases (just to end up discovering in the end that it was a bug that has already been fixed) when we also have tickets and bug reports that need to be addressed on the current builds. You should usually always make backups before upgrading, just in case something does happen. Second, I'm not aware what time it is where you reside, but it was roughly 1:30AM Eastern Time when you opened your ticket, so support times are naturally going to be a bit slower. You then received a reply only 7 minutes after opening the ticket informing you that you accidentally posted your ticket in the wrong department, and that the ticket was being moved for you. Keep in mind our SLA is actually 48 hours, and your tickets are all being addressed well within this time window. I see you have also already received a reply to your ticket from Marc as well. As he told you, uploading a new copy of files from all products should not cause you any issues whatsoever, assuming the files were uploaded correctly. The most likely issue is that you have accidentally uploaded the wrong version of Nexus, in which case re-uploading everything with the correct package should resolve the problem.
  10. Double redirects are fine. It's only once you start going over 3 redirect chains that it can become a problem.
×
×
  • Create New...