Not my style to take to twitter unless I get really crappy service. And really crappy service is not really something I’m prone to getting from the SS community tbh! hehehe
Where should I report (or check it’s already been reported) an issue with the rendering int he new Docs layout?
The url_variable_tools page is rendering so it’s almost unreadable. Hard to actually determine what’s what.
Chrome latest stable. https://docs.silverstripe.org/en/4/developer_guides/debugging/url_variable_tools/
Is there anyone here using https://github.com/jinjie/codeeditorfield ?
I’m finding a weird behaviour. When an edit form is first rendered the field doesn’t render at all. It displays as if it was a ReadOnlyField simply displaying the raw text. If the form is refreshed, the field then renders correctly. The difference I’ve found is that the jinjie/codeeditofield resources somehow are not being triggered (and thus don’t execute to modify the behaviour). Seems that the entwine code in the module is not getting called on the first load?
SilverStripe 4.3.x, CodeEditorField v 0.0.3 (latest master)
Code Editor Field for SilverStripe 4. Contribute to jinjie/codeeditorfield development by creating an account on GitHub.Hide attachment content
Hi people! My google-fu is failing me. I have a
searchable_fields array defined on my object but the ID field never appears in the search dropdown above the gridfield in the CMS. All the other fields appear with their scaffolded defaults (where appropriate) but the ID field does not appear in the detail form at all. I have tried just using
ID and letting it default to normal scaffolding but even then it doesn’t appear in the form. I would appreciate some help 🙂 . SS4.3.3
- private static $searchable_fields = [
- 'Title' => 'PartialMatchFilter',
- 'ID' => [
- 'title' => 'Promotion ID',
- 'field' => NumericField::class,
- 'filter' => 'PartialMatchFilter'
Those rates seem low, from anecdotal experience among colleagues currently.
Update: Issue resolved. We had a minor bug in the virtual host config that was breaking. All is serene now and our site is building correctly in the on-demand environments.
These are the SS assets - not our website assets - things like vendor files, etc.
Hi all. We’re deep in the process of migrating from SS3.x latest to 4.x latest and hitting some apache issues. We’re getting a lot of
net::ERR_ABORTED 404 errors looking for assets, etc. Currently we have SS installed in the docroot. Can anyone offer some leads to investigate? My google-fu is failing me today and I’m struggling to find any solutions online that are having the desired effect.
FYI: The SS build works correctly in localhost. This is when we are trying to run it in an on-demand environment.
Oi vey - my google-fu must be failing big time. I didn’t even see those docs 😞
Hi Team! Has anyone had any experience using Mockery with SS tests for stubs and spies? Any alternative recommended plugins for this sort of functionality?
There’s an old testing library called Phockito which we used to use in some of the semi core modules, I think that used Mockery. We have since refactored it all out though because it wasn’t really needed over a standard phpunit test