I just started to set up pagination with Jekyll. While I was following a tutorial, I recognized that message saying there was a newer version. So, I followed this and copy pasted the first example given in the gem repository of jekyll-paginate-v2 which I found on GitHub.
Unfortunately this is not going to work, telling me that I would combine new and old pagination logic. The error is:
AutoPages: Disabled/Not configured in site.config.
Pagination: Legacy paginate configuration settings detected and will be used.
The new jekyll-paginate-v2 and the old jekyll-paginate logic cannot both be configured in the site config at the same time. Please disable the old 'paginate:' config settings by either omitting the values or setting them to 'paginate:off'.
Traceback (most recent call last):
...
.../paginationGenerator.rb:37:in `generate': The new jekyll-paginate-v2 and the old jekyll-paginate logic cannot both be configured in the site config at the same time. Please disable the old 'paginate:' config settings by either omitting the values or setting them to 'paginate:off'. (ArgumentError)
I omitted the file references to jekyll (none of my files was listed). Also I do not see a file called site.config (neither in my coder nor in the examples). What is wrong with my setup?
Related
Until recently everything was working well. Now, when I try to save (create or update) any page or post I get error message at top of the form "Error - There was an error when trying to save the form".
In error log I see this error:
“Uncaught PHP Exception Sulu\Component\Rest\Exception\InvalidHashException: “The given hash for the entity of type “Sulu\Bundle\ArticleBundle\Document\ArticleDocument” with the id “9e0720a7-5565-4a6f-a735-8a186b8fef9b” does not match the current hash. The entity has probably been edited in the mean time.” at /var/www/html/vendor/sulu/sulu/src/Sulu/Component/Hash/RequestHashChecker.php line 53"
Tried clearing symfony cache, website cache from admin, restarting docker containers.
I'm totally unaware that I did something to cause this error. Please help.
Update: strange thing I just noticed. When I try to save some article and I get that error and go back to overview page (where i.e. all articles of that type are listed) then I see unchanged article title. But when I click to edit it I see changed title?!? Like title on overview page and title on edit page are not used from the same place? How is that possible?
Update:
Now even I setup once more project from scratch saving articles causes that error. Some more info:
In stack trace last command executed is:
in vendor/elasticsearch/elasticsearch/src/Elasticsearch/ConnectionPool/StaticNoPingConnectionPool.php (line 64)
an it shoots out “No alive nodes found in your cluster”.
And while I'm setting up the project when executing:
php bin/console ongr:es:index:create
I get error:
{"error":{"root_cause":[{"type":"resource_already_exists_exception","reason
":"index [su_articles/sWs5F1uzSFO8bFiZqF1Egw] already exists","index_uuid":
"sWs5F1uzSFO8bFiZqF1Egw","index":"su_articles"}],"type":"resource_already_e
xists_exception","reason":"index [su_articles/sWs5F1uzSFO8bFiZqF1Egw] alrea
dy exists","index_uuid":"sWs5F1uzSFO8bFiZqF1Egw","index":"su_articles"},"st
atus":400}
And when I run:
php bin/console ongr:es:index:create --manager=live
I get similar:
In Connection.php line 675:
{"error":{"root_cause":[{"type":"resource_already_exists_exception","reason":"index [su_articles_live/Pissm9ycRj-o79K4wrrD
AA] already exists","index_uuid":"Pissm9ycRj-o79K4wrrDAA","index":"su_articles_live"}],"type":"resource_already_exists_exc
eption","reason":"index [su_articles_live/Pissm9ycRj-o79K4wrrDAA] already exists","index_uuid":"Pissm9ycRj-o79K4wrrDAA","i
ndex":"su_articles_live"},"status":400}
Also to mention that now saving pages works, but saving articles doesn't.
This solved the issue on ElasticSearch index creation for me:
php bin/console ongr:es:index:drop --force
The error can happen in the following cases.
Expected Case somebody else did edit the same article like you and did save it
Unexpected Case your phpcr cache is not in sync
Unexpected Case you have a multi server setup but your cache.app is not configured to use a central cache
So if its one of the unexpected cases first you should clear your cache.pools with:
bin/console cache:pool:prune
If you have a multi server setup make sure you configure a central cache. Most use in this case a redis-server which you configure in your cache.yaml e.g.:
# config/packages/prod/cache.yaml
framework:
cache:
default_redis_provider: "%env(resolve:REDIS_DSN)%"
app: cache.adapter.redis
Also make sure that you use the latest version and maybe update your phpcr cache configuration based on the sulu/skeleton: https://github.com/sulu/skeleton/blob/2.x/config/packages/prod/sulu_document_manager.yaml, there you could when performance doesn't matter in your case disable the phpcr cache, I would not recommend that.
I am trying to add a blog to a SilverStripe site using the Blog Module.
The package seemed to install fine (via composer require silverstripe/blog) and dev/build returned no errors. The ‘Blog’ page type is also available from the ‘Add page’ menu.
After adding a ‘Blog’ page, the site doesn’t redirect to http://localhost:8888/example/admin/pages/edit/show and simply remains on the http://localhost:8888/example/admin/pages/add/ page.
From what I can tell, the only result from this action is an ‘ARCHIVED’ page being added to the sitetree.
Have ?flush=all etc as per other suggestions to no avail and other page types are still being added fine.
Does anyone have any idea what might be going on here?
Currently using:
"silverstripe/cms": "3.6.1",
"silverstripe/framework": "3.6.1",
"phpunit/PHPUnit": "~3.7#stable"
"silverstripe/blog": "2.4.6"
[Edit 13/09/2017]
While simply adding a 'Blog' page produces no observable errors, adding a generic 'Page' and changing the page type to 'Blog' produces the following error in the php_error.log:
PHP Warning: require_once(/Applications/MAMP/htdocs/example/blog/_config.php): failed to open stream: No such file or directory in /Applications/MAMP/htdocs/example/framework/core/manifest/ConfigManifest.php on line 141
PHP Fatal error: require_once(): Failed opening required '/Applications/MAMP/htdocs/example/blog/_config.php' (include_path='/Applications/MAMP/htdocs/example/vendor/phpunit/phpunit-mock-objects:/Applications/MAMP/htdocs/example/vendor/phpunit/php-token-stream:/Applications/MAMP/htdocs/example/vendor/phpunit/php-code-coverage:/Applications/MAMP/htdocs/example/vendor/phpunit/phpunit:/Applications/MAMP/htdocs/example/vendor/symfony/yaml:.:/Applications/MAMP/htdocs/example/framework:/Applications/MAMP/htdocs/example/framework/parsers:/Applications/MAMP/htdocs/example/framework/thirdparty:.:/Applications/MAMP/bin/php/php5.6.30/lib/php') in /Applications/MAMP/htdocs/example/framework/core/manifest/ConfigManifest.php on line 141
[Edit 13/09/2017]
Trialled the module on a clean install of SilverStripe as well as another project (both using 3.6.1 CMS and 2.4.6 Blog module); both work so far without issue. Perhaps it was an issue with this particular project. Would still be great to get clarification on what the root of this issue might have been.
I have been using Jekyll and a Jekyll theme for my blog hosted on GitHub Pages. I haven't blogged in a few months, and today, before pushing to GitHub, I ran jekyll serve and received multiple errors, including:
Deprecation: The 'include' configuration option must now be specified as an array, but you specified a string. For now, we've treated the string you provided as a list of comma-separated values.
I also received another error:
Error: could not read file /Users/JakeWengroff/blog/pages/_posts/2016-07-28-blog-title.md: (<unknown>): mapping values are not allowed in this context at line 5 column 71
And when viewing my blog with localhost:4000, the newest post does not appear but all past posts do.
Despite these errors, I pushed the new post to GitHub, visited my blog's URL, and the same situation occurred: my most recent post does not appear, although all previous posts do.
I do know that Jekyll recently upgraded to v.3.2.0, though after reviewing the documentation, I could not seem to find any changes that address my error today. I also checked the Jekyll troubleshooting pages and again, I could not find anything that would address this issue.
The upgrading from Jekyll 2 to 3 page suggested adding future: true to the _config.yml page. I did that, and still, nothing.
Any help would be greatly appreciated. Thank you!
For your first error:
In your config file, change
include: _portfolio
to:
include:
- _portfolio
And for your second error, change this line, from:
summary: Data scientists do not usually create their own algorithms: what a relief.
to:
summary: "Data scientists do not usually create their own algorithms: what a relief."
Note that I just put the line in quotes because you've got a colon in the value, which Jekyll uses to differentiate between keys and values in front matter.
I have just upgraded from kendoui.web.2013.1.514 to kendoui.web.2013.2.716 and have noticed that in the parts of the code where I require (through require.js) a certain kendo.culture.xx-XX.min.js file that also an unsuccessful request for kendo.core.min.js happens and I get an error in the console.
This did not happen with kendoui.web.2013.1.514 and I think this part inside the kendo.culture.xx-XX.min.js files might be to blame:
("function"==typeof define&&define.amd?define:function(e,n){return n()})(["../kendo.core.min"]
Also this reference to kendo.core appears to only be present in the minified versions. Note that I already have kendo.web.min.js fully loaded and the app works fine even with the invalid request so is this a bug?
If you are using the bundles (i.e. kendo.web.min.js) then you shouldn't use RequireJS to load them or any culture files.
I'm sorry that the documentation didn't mention it, I just added a section to explain this.
I can't get the Bisna doctrine cli to work. It complains about not being able to find the Symfony Console application. Notice it's trying to look for it in a nested directory of Doctrine/Symfony/Console/Symfony/Component/Console. Anybody ever seen this?
PHP Warning: require(/Users/jhicks/workspace/production/application/../library/Doctrine/Symfony/Console/Symfony/Component/Console/Application.php): failed to open stream: No such file or directory in /Users/jhicks/workspace/production/library/Doctrine/Common/ClassLoader.php on line 163
PHP Fatal error: require(): Failed opening required '/Users/jhicks/workspace/production/application/../library/Doctrine/Symfony/Console/Symfony/Component/Console/Application.php' (include_path='/Users/jhicks/workspace/production/library:.:/opt/local/lib/php') in /Users/jhicks/workspace/production/library/Doctrine/Common/ClassLoader.php on line 163
Here's the Github page for the doctrine cli from Bisna: https://github.com/guilhermeblanco/ZendFramework1-Doctrine2/blob/master/bin/doctrine.php
There are many repositories that call themsemves Bisna in Github, it is difficult to find what of them you are using without further information.
The original one is the one created by Guilherme Blanco (Bisna used to be his nickname) called Zend Framework 1 + Doctrine 2 and works like a charm, but it does not bundle the Symfony components necessary to run the CLI tool.
What you have to do is download them from GitHub (search for "Symfony" and you will find the components inside the Organization repository) and put them inside your project's library folder paying attention to the PSR #0 naming conventions.
If you provide the piece of code that generates this error and the repository and version you are using, it will be easier to detect the error and give a better answer. It is naive to try and guess the type of error, but probably you have problems with namespaces and/or how you are calling Symfony's Console component.
If you need some guidance on how this integration can be achieved, you can look at doctrine.php inside Blanco's repository.
Looks like I needed to add these two lines to my existing autoloader bootstrap method:
$symfonyAutoloader = new \Doctrine\Common\ClassLoader('Symfony', 'Doctrine');
$autoloader->pushAutoloader(array($symfonyAutoloader, 'loadClass'), 'Symfony');
I didn't think this would be necessary since I included Symfony in the autoloaderNamespaces array in my application.ini file.
autoloaderNamespaces[] = "Symfony"