Silverstripe CMS 是否像看上去那样易于部署、维护和开发？
虽然我没有考虑过将其部署在我自己的网站上，但我认识的人向我发送了一个名为 SilverStripe 我以前从未听说过。 我阅读了他们的网站，查看并试用了他们的演示，等等。 它看起来像是一个由自定义 PHP 框架（他们称之为 Sapphire）支持的 CMS。 从我在他们的网站上收集到的信息以及使用他们的演示来看，它可能会像他们所说的那样好又容易（一旦你克服了任何学习曲线，考虑到它看起来很像其他 PHP 框架，而且它看起来很小，并且CMS）。
这里有人曾经使用 SilverStripe 部署、维护或开发过 CMS 吗？ 如果是这样，您能否从开发人员的角度解释一下？
我还在 StackOverflow 上发现了有关 SilverStripe 的早期问题，但从开发的角度来看，我比用户或管理员的角度更感兴趣。
Although I haven't thought about deploying it on my own site, someone I know sent me a link to a CMS called SilverStripe that I've never heard of before. I read their site, looked at and played around with their demo, and so on. It looks like it's a CMS backed by a custom PHP framework that they call Sapphire. And from what I can gather on their website and using their demo, it potentially might be as good and easy as they say (once you get past any learning curve, which appears to be small, considering it looks a lot like other PHP frameworks and CMSes).
Has anyone here ever deployed, maintained, or developed a CMS using SilverStripe? If so, could you shed some light on it, from a developer's point-of-view?
I also found this earlier question about SilverStripe here on StackOverflow, but I'm more interested from a development point of view than a user or administrator point of view.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我使用 Silverstripe 为多媒体和娱乐行业的一家公司开发了一个流量很大的网站。 大部分工作是一年前完成的，但增强和维护工作仍在进行中。 如果您愿意，我可以为您提供具体细节 - 在 Twitter 上私信我或给我发电子邮件。
简而言之：如果我能回到过去并在另一个 PHP CMS/框架中重做，我可能会使用 Drupal。
它非常适合不太深也不太宽的简单网站。 但任何具有复杂 IA 的网站都可能会遇到麻烦。
我遇到的一些问题：
文档不完整、支离破碎，在许多情况下，甚至不存在。
随着网站变得越来越宽和，管理界面很快就会变得站不住脚。 他们通过 JavaScript 加载每个窗格，而在速度较慢的计算机上，速度就慢得像爬行一样。 （com.wiki 注释：在 2.4 中修复）
Silverstripe 无法拥有超出第一级的 URL。 意思是，它们只允许像
/about这样的 URL，而不是/about/team。 您需要执行/about_team。 （维基注释：在 2.4 中修复）Sapphire 和 Silverstripe 之间的分离很脆弱。 尽管已经尝试将两者松散耦合，但很难真正将它们分开。 （注：2.4 中好多了）
每个主要内容类型都存在于站点树上。 Silverstripe 是一个严格基于页面的 CMS。 例如，在创建博客文章时，每个单独的博客文章都是站点树上的一个项目。 这使得在扩展具有数百篇博客文章的网站时变得不切实际。 （注意：已在 2.3 - ModelAdmin 中修复）
坦白说，它很慢。 管理员很慢。 前端速度很慢。 操作码缓存有帮助，但仍然很慢。 （维基注释：2.4 中更好）
模板系统很奇怪。 它允许您使用自定义 HTML，这很好，但模板标签有一点限制。 例如，模板中的 if 条件只能排除单个
AND或OR。 你不能将多个链接在一起。有问题。 在开发过程中，我修复了 Silverstripe 核心中至少 10 个错误。 我提交给他们的错误跟踪器的错误几个月都没有得到修复，即使修复很简单。
I used Silverstripe to develop a heavily trafficked site for a company in the multimedia and entertainment industry. Most of the work was done a year ago, but there has been on going enhancement and maintenance work. I can give you specific details if you want -- DM me on Twitter or email me.
In short: if I could go back in time and do it over in another PHP CMS/Framework, I'd probably have used Drupal.
It could work well for a simple site that's not too deep and not too wide. But any site that has a complex IA will likely run into trouble.
Some issues I ran into:
Documentation was incomplete, fragmented and in many cases, non-existent.
The administration interface quickly becomes untenable with a site becomes wide and deep. They load every pane via javascript, and things slow to a crawl on a slow computer. (com. wiki note: fixed in 2.4)
Silverstripe is incapable of having URLs beyond the first level. Meaning, they only allow urls like
/aboutand not/about/team. You'd need to do/about_team. (wiki note: fixed in 2.4)The separation between Sapphire and Silverstripe is tenuous. Although an attempt has been made to loosely couple the two, it's difficult to truly separate them. (note: much better in 2.4)
Every major content type exists on the site tree. Silverstripe is a strictly page based CMS. For example, when creating blog posts, each individual blog post is an item on the site tree. This makes it impractical when scaling out a site with hundreds of blog posts. (note: fixed in 2.3 - ModelAdmin)
Frankly, it's slow. The admin is slow. The front-end is slow. opcode caching helps, but it's still slow. (wiki note: better in 2.4)
The templating system is weird. It allows you to use custom HTML, which is nice, but the template tags are a little limited. An if conditional in a template, for example, can only except a single
ANDorOR. You can't chain multiple ones together.It's buggy. During the course of development, I fixed at least 10 bugs in Silverstripe core. Bugs I submitted to their bug tracker were not fixed for months, even when the fix was simple.
顺便说一句，2.4 真是太棒了。 现在任何想了解 SilverStripe 的人都应该毫不犹豫。 文档仍然有点薄弱，但我无法再使用 WordPress、Drupal 或 Concrete5。
现在，由于文档很薄弱，请获取 SilverStripe 书籍并查看 2.4 更改/升级 wiki 页面： http://doc.silverstripe.org/upgrading:2.4.0
2.4 is amazing by the way. Anyone wondering about SilverStripe now should not hesitate. Documentation still a little weak, but I cannot bring myself to use WordPress, Drupal or Concrete5 anymore.
Now, being that the documentation is weak, please get the SilverStripe book and review the 2.4 changes/upgrade wiki page: http://doc.silverstripe.org/upgrading:2.4.0
感谢您的评论 - 了解 SilverStripe 项目应该关注的内容很有用。 您会很高兴地知道，您提出的问题是我们最近一直在认真研究的领域：
现在，我们距离为开发人员提供 450 页的 SilverStripe 书籍还有很大的改进。文档（请参阅 http://www.silverstripe.org/silverstripe-book/）它将解释为什么我们的模板语言故意简单。
即将发布的 2.4 版本的工作与性能相关，并且可能有助于分离 CMS/Sapphire（并删除 jsparty 文件夹）和解决您遇到的其他错误。 在向我们提供补丁/修复方面，非常感谢； 作为一个开源项目，我们依赖于此。 关于您的缓慢和错误，请继续在 open.silverstripe.com 上详细提出问题，以便它们获得可见性并可以由核心团队或其他社区成员处理:)
Sigurd，SilverStripe。
thanks for your comments - it is useful to know what the SilverStripe project should focus on. You'll be pleased to know that the issues you raise are areas that we've been working on in serious ways recently:
Right now we're a few weeks away from having a 450 page book on SilverStripe for developers that will greatly improve our documentation, (see http://www.silverstripe.org/silverstripe-book/) and it will explain why our templating language is intentionally simple.
The work on the upcoming 2.4 release relates to performance, and may help in terms of separation of CMS/Sapphire (and removes the jsparty folder) and solving other bugs you're encountering. In terms of supplying us with patches/fixes, thanks very much; being an open source project we depend on that. In terms of your slowness and bugs, please continue to raise the issues in detail at open.silverstripe.com so that they get visibility and can be worked on by the core team or other community members :)
Sigurd, SilverStripe.
我做过几个SS 网站，没什么大的，还有一个类似于小型CRM 的应用程序。
我从来不喜欢任何 CMS 解决方案，我宁愿在 Zend FW 之上构建一个。 但 SS 是不同的，说实话，我使用它越多，我就越喜欢它。 如果它位于 Zend FW 之上，我会更高兴:)但是...
如上所述，模板有一些限制
另外，您不能包含已包含的部分。
我喜欢它，因为你不会花太多时间在管理上，而是花更多的编码时间。 而且它正在快速成熟，所以我会对它充满信心。
I have done few SS sites nothing big, and a application that is like a small CRM.
I never liked any of CMS solutions, id rather build one on top of Zend FW. But SS is different and to be honest the more I work with it the more i like it. I would be more happy if it was on top of Zend FW :) but...
There are some limitations with the templates as mentioned
plus you cant include in the already included parts.
I like it cause u dont spend much time in the admin but more coding. And it is maturing fast, so I will put my faith in it.
因为我是一个“新手”，所以我只能在上一个回复中粘贴一个链接，所以，继续：
请参阅本书勘误表，尽管那些 2.4 注释已移至上一个链接： http://doc.silverstripe.org/silverstripe-book-errata
祝你好运并享受。 我真的很喜欢这个系统的强大功能和易用性。 我唯一希望看到添加的是内容的前端内联编辑，但 CMS 只是背面的杀手，不容忽视。
And because I'm a "newbie" I could only paste one link in the previous reply so, continuing:
As well see the book errata, although those 2.4 notes were moved to the previous link: http://doc.silverstripe.org/silverstripe-book-errata
Good luck and enjoy. I truly enjoy both the power and ease of this system. The only thing I would like to see added is frontside inline editing of content, but the CMS is just killer on the back and cannot be ignored.