i have installed silverstripe comment module but the comment form on page is not appearing also as they said in installation.md
Out of the box the module adds commenting support to all pages on your site. This functionality can be turned on and off on a per page basis in the CMS under the Behaviour tab for a given page. Once the Allow Comments checkbox is ticked, republish and view the webpage.
but the Allow Comments checkbox is not appearing too
here's my composer.json :-
{
"name": "silverstripe/installer",
"description": "The SilverStripe Framework Installer",
"require": {
"php": ">=5.3.3",
"silverstripe/cms": "3.2.1",
"silverstripe/framework": "3.2.1",
"silverstripe/reports": "3.2.1",
"silverstripe/siteconfig": "3.2.1",
"silverstripe-themes/simple": "3.1.*",
"assertchris/hash-compat": "^1.0",
"colymba/gridfield-bulk-editing-tools": "^2.1",
"silverstripe/comments": "^2.0",
"silverstripe/lumberjack": "^1.1",
"silverstripe/tagfield": "^1.2",
"silverstripe/blog": "^2.3"
},
"require-dev": {
"phpunit/PHPUnit": "~3.7"
},
"config": {
"process-timeout": 600
},
"prefer-stable": true,
"minimum-stability": "dev"
}
what am i missing?
Just add
SiteTree:
extensions:
- CommentsExtension
comments:
require_login: true
in /mysite/config.yml
Then simply "/dev/build?flush=1"
Related
I'm using the command standard-version each time I want to publish new version, but the yielded changes in the CHANGELOG.md look like this:
### [10.1.9](https://github.com/my-project-name/compare/v10.1.8...v10.1.9) (2021-03-29)
### [10.1.8](https://github.com/my-project-name/compare/v10.1.7...v10.1.8) (2021-03-29)
### [10.1.7](https://github.com/my-project-name/compare/v10.1.6...v10.1.7) (2021-03-29)
first the links do not work - the github url is not correct and i want to configure it to the right url, and second, I'd like to configure the link that's shown in the changeslog file (there are some types)
I tried to use this documentation but didn't find anything that can help me
https://github.com/conventional-changelog/conventional-changelog
so how do I configure the way standard-version works on the CHANGELOG.md ? can someone provide example?
yes.
according to doc:
You can configure standard-version either by:
Placing a standard-version stanza in your package.json (assuming your project is JavaScript).
Creating a .versionrc, .versionrc.json or .versionrc.js.
If you are using a .versionrc.js your default export must be a configuration object, or a function returning a configuration object.
Any of the command line parameters accepted by standard-version can instead be provided via configuration.
Please refer to the conventional-changelog-config-spec for details on available configuration options.
example:
.versionrc
{
"types": [
{
"type": "feat",
"section": "Features"
},
{
"type": "fix",
"section": "Bug Fixes"
},
{
"type": "chore",
"hidden": true
},
{
"type": "docs",
"hidden": true
},
{
"type": "style",
"hidden": true
},
{
"type": "refactor",
"section": "Refactor"
},
{
"type": "perf",
"section": "Performance"
},
{
"type": "test",
"hidden": true
}
]
}
How can one include UX package with the extjs open tooling?
I would like to use Ext.ux.ajax.SimManager
in app.json:
"requires": [
"font-awesome",
"ux"
],
package.json:
"dependencies": {
"#sencha/ext-modern": "~7.0.0",
"#sencha/ext-modern-theme-material": "~7.0.0",
"#sencha/ext": "~7.0.0"
},
I've tried to add "#sencha/ext-ux": "~7.0.0" but without success
After updating Vue CLI 3 to CLI 4 the service worker stopped being registering.
Ennvironment:
Firebase hosting,
"vue": "^2.6.10",
"vuex": "^3.1.1",
"firebase": "^7.2.3",
"vuetify": "^2.1.9",
"core-js": "^3.3.6",
...
"#vue/cli-plugin-pwa": "^4.0.5",
I see the fail is on the generated precache-manifest file exactly on the /index.html page:
// precache-manifest.326028534d4ff40f4be7a15fc11e84c6.js
...
{
"revision": "7eeb3269c508ac628b85ccfaa20744ab",
"url": "/index.html"
},
...
I tried to disable 'skipWaiting' from the workboxOptions because I use lazy-loading routes as the documentation says, but it doesn't do anything:
pwa:{
workboxOptions: {
skipWaiting: false,
}
}
The error in the network tab is:
If I comment out the lines in the compiled precache-manifest file manually then the service worker works without a problem. I don't understand.
It turned out the problem was in the configuration of firebase.json, in the section of hosting, I hade enabled "cleanUrls": true. Removing it made the service worker register again.
this is how it looks now, the default settings:
"hosting": {
"public": "dist",
"ignore": [
"firebase.json",
"**/.*",
"**/node_modules/**"
],
"rewrites": [
{
"source": "**",
"destination": "/index.html"
}
]
},
I'm making my first desktop application using node-webkit.
I followed all the steps to package the app on windows but I'm getting this error:
There is no 'package.json' in the package, please make sure the 'package.json' is in the root of the package.
Although the package is in the root.
sample package.json file
{
"name": "name of app",
"version": "1.0.0",
"main": "index.html",
"single-instance": true,
"node-remote": "<local>",
"window": {
"title": "name to show in title bar",
"icon": "icon to show in titlebar",
"position": "center",
"min_width": 1024,
"min_height": 600,
"toolbar": true,
"width": 1362,
"height": 768
},
"dependencies": {
"express": "3.x"
},
"webkit": {
"plugin": true
}
}
Ok I found my mistake. In fact, I was compressing the folder containing the package json and the other files. So what I made was like that:
App.zip
|
|-App
|-package.json
|-Other files
What is correct is this:
App.zip
|-package.json
|-Other files
as per the documentation:
http://symfony.com/doc/current/book/security.html#retrieving-the-user-object
I am trying to use twig to check to see if the user is authenticated
when i put in my twig templates:
{{ app.user.username }}
I get the error
LogicException: Unable to add global "app" as the runtime or the extensions have already been initialized.
EDIT: Please find as per below the composer.json contents
{
"name": "symfony/framework-standard-edition",
"description": "The \"Symfony Standard Edition\" distribution",
"autoload": {
"psr-0": { "": "src/" }
},
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.*",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.*",
"twig/extensions": "1.0.*#dev",
"symfony/assetic-bundle": "2.1.*",
"symfony/swiftmailer-bundle": "2.1.*",
"symfony/monolog-bundle": "2.1.*",
"sensio/distribution-bundle": "2.1.*",
"sensio/framework-extra-bundle": "2.1.*",
"sensio/generator-bundle": "2.1.*",
"jms/security-extra-bundle": "1.2.*",
"jms/di-extra-bundle": "1.1.*",
"kriswallsmith/assetic": "1.1.*#dev",
"doctrine/data-fixtures": "dev-master",
"doctrine/doctrine-fixtures-bundle": "dev-master"
},
"scripts": {
"post-install-cmd": [
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap",
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache",
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets",
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap",
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache",
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets",
"Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
}
Its hard to answer to this question without more details.
First, please notice that there have been such a similar exception in the past, due to a Symfony2.1 bug which has been solved with a recent release: see here for more details.
Then, notice that the error seems to be thrown in addGlobal function of class Twig_Environment. Did you installed such Twig Extension?
Without reading your composer.json, I can suggest to try to:
Clear the cache.
update the code in your composer.json, to avoid the presence of up to date bundles.
Create the composer.phar.
Then compile it to get the composer.phar.
php composer.phar install or php composer.phar update, whatever be your case.
Hope it helps.