I wanted to know why AsseticBundle has been removed from all the versions of Symfony.
I looked everywhere and I don't found any site talking about this news that began for some weeks.
Initially, I thought they deleted this Bundle because there is a security flaw that will take a few days to be repaired.
This Bundle is indisponsable for including javascript and css file type from an external folder and I wanted to be sure if this Bundle wille be replaced by an another in Symfony or I should add this Bundle manually.
Thanks
The AsseticBundle is not compatible/maintained with the new version of the framework (2.8/3.x).
See the tweet of Fabpot that asking: Honest question: is #Assetic still relevant for #Symfony 3.0?
And the PR remove AsseticBundle (you can find good discussion about for and against the removal of Assetic).
Check also this great article on Symfony and Asset Management that clarify and riassume all the discussion around.
Hope this help
Although Symfony does not support assetic from versions 2.8 upwards, you can still install it by running:
composer require symfony/assetic-bundle
and then enable the bundle in your AppKernel.php like so:
new Symfony\Bundle\AsseticBundle\AsseticBundle()
Related
A couple of years of go i used to program using PHP, but without frameworks. With these recent developments I've decided to get in the to the game and try using one. I've decided to use yii 2.0 .
I've read some of the documentation and in my opinion there is some lack of information (at least for who is getting started), so i´m having some problems installing yii 2.0 on my computer using Xampp. The PHP version is 5.5.9.
From what i could understand i downloaded the yii 2.0 framework, extracted the content and copied to c:\xampp\htdocs\yii2
I've already installed the composer, so the the next thing to do i think would be, using the cmd, do these two lines of code:
composer global require "fxp/composer-asset-plugin:1.0.0"
composer create-project --prefer-dist --stability=dev yiisoft/yii2-app-basic basic
The problem is when i do the last one it asks for username and password i think of GitHub. Can you tell me if I'm obligated to have an account on github to install yii 2.0 framework.
Is there a way to get around this?
Yii2 is integrated with composer asset plugin. It allows download Bower and NodeJs packages through Composer.
Github account is required to overcome API rate limit. Here is the explanation from the main contributor of this extension:
It's a rate limit of Github API. In anonymous access, Github at a
greatly reduced limit (60/hr it seems to me), and we must be logged
with a token for have a much higher limit.
See composer/composer#1569 and composer/composer#1877
The problem also exists using Nodejs and Bower.
You can find it in this issue, it's 9th from the top.
I think workaround with installing Bower and the same packages is not an option, because initially and with each framework update you must manually synchronize packages with their versions and override some configuration. Also some extensions require javascript plugins and using composer asset plugin too. So you have to do the same with each of them too. It simply not worth it. And having account on Github for web developer nowadays is kind of de facto standard.
Just create Github account if you are still don't have one and everything should be fine. Earlier updating process was pretty slow, now it's faster and I found this approach pretty interesting and flexible.
Asked this on superuser.com, not sure if stackoverflow is a better suitable place for it, but I am not getting any answers yet:
===
I am trying to generate a new blog entry in my octopress setup, but I noticed that some previous posts are being generated as empty files in public, so are the new ones I am trying to generte.
There seems to be no difference at all between the markup files from one entry which is being properly generated to another that isn't
I've got two octopress installations, one's working and this one I am talking about isn't, updates octopress on both, reinstalled bundle but no luck, files as atom.xml are also not being generated correctly.
Also updated from ruby 1.9.2p290 to latest release from 1.9.3 but also did not difference.
Anyone's encountered this before?
===
This is most likely because you started using codeblocks. This was happening to me, and even posts/pages that didn't use codeblocks would fail to generate. My problem (on Windows) was that I didn't even have Python installed (thought I did). Installing it fixed the problem, then gave me another error, which was fixed by updating the pygments.rb (note .rb) gem. Doing these two things fixed all my problems.
There's a similar issue if you're on arch linux which defaults python to version 3 which isn't supported by pygments.rb yet. You'll have to look around to figure out how to fix that to use 2.7 instead, but it should be pretty straightforward.
Can you provide an example of: a) a post that doesn't generate correctly, and b) a post that does generate correctly?
I assume they are just individual posts (and not, for example, pages like /about/). I would also assume that they render as blank both in the blog index on your front page and on the individual post page.
Also - what does render? Is it rendering the rest of the page, but just without the "content" of the post itself? Or does the page not even exist? (404?)
I'm looking for Symfony2 forum bundle, which is:
working
not dead
supports sf 2.1
Anyone knows of such a thing?
check this one out:
http://packagist.org/packages/herzult/forum-bundle
It has been updated recently and it is symfony 2.1 ready. You can install it through composer.
Also check http://packagist.org/packages/friendsofsymfony/comment-bundle that allows you to threading capabilities to your symfony application.
You can always check http://packagist.org for symfony 2.1 ready bundles ;)
If you have any problem instaling these feel free to ask.
after upgrading to sass-3.1.8 form sass-3.1.7 I get this error:
Functions may only be defined at the root of a document.
any Idea how I can solve this?
I'm using some of bourbon's mixins and it's imported at the top of my stylesheets, that's all.
I have the same problem and could not solve it by modifying code.
The way I solved was to use an older version:
gem uninstall sass
gem install sass -v 3.1.1
Ok Here is what I come up with:
SASS team decided to make a change (in this case "Functions may only be defined at the root of a document.") that made some plugins incompatible. in my case it was bourbon library. I made a ticket on github homepage of the bourbon and the owner updated the code and released a new version that's working with latest api.
I think this change should have got a bigger version bump to indicate the api change.
Sass developer here. Mixins and functions were never meant to be allowed in a scoped context. A bug was fixed recently that caused them to be caught when in an imported file (before this fix they were only caught if defined in the primary sass file).
That said, it's not a feature we're explicitly opposed to, but we'd would need to properly test it, document it, and support it as an official feature.
I'm new to CI. Anyone could help to the latest version of CI. most of the Tutorial is for last version and it didn't work for the latest version. please help.
You can still get started using what's availabe for 1.7, if you pay attention to how file structure changed between the two versions (ie the System and Application directories are now separate). To that, many of the tuts you'll find are applicable - bearing in mind that the paths may differ, and you'll want to verify that the functions are still supported in 2.0 by use of the User's Guide).
If you walked through the tut in your link, using the Models, Views, Controllers directories inside Application, you'd get a "Hello World" page.
The User's Guide is a great tool, as are the Community Forums.
Best of luck to you.
I recently migrated a site using CodeIgniter from 1.7 to 2.0. - I found the following link to be very useful:
http://philsturgeon.co.uk/news/2010/05/upgrading-to-codeigniter-2.0