I use SonataMediaBundle with SonataAdminBundle with a simple install.
When i want to add a new media. I can select what provider i want. I configured it to show Daylimotion, Youtube and Image.
The Youtube and Image picture doesn't appears. I can see the error
GET http://my_url/web/data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAOcA…/kI5CVlcXzqGKBtUyZMjz8qd9WApPTb0NUnhAgBPwh8D8I22yw4XkRvwAAAABJRU5ErkJggg== 414 (Request-URI Too Long)
Second problem come when i upload an image. I got:
request failed: URI too long (longer than 8190)
I try the js i found at http://sonata-project.org/bundles/admin/master/doc/reference/troubleshooting.html but it doesn't work.
Edit: I change my SonataMediaBundle version from 2.3 to dev-master. Now i can see the youtube logo but still have the too long uri error.
I faced the same issue. I was using the sonata core 2.3.1 and changed to 2.3.0, This solved it. It seems that the 2.3.3 also having the same issue.
So make sure you downgrade your sonata core in composer.json until they fixed the issue. It is better to downgrade to a stable version than using the dev branch.
"sonata-project/core-bundle": "2.3.0"
By the way, i'm using the 2.3.1 for MediaBundle.
issue
Problem solved with an update to dev-master and a cache:warmup !
Please use only stable version otherwise you might have some WIP issues...
Related
let me know if anyone else, also having the same issue. it is working fine with older version but I just installed the latest version and now it's not working.
I have faced the same problem today in morning when I have updated WordPress to latest version 5.
But I have fixed the Problem by updating the Visual-composer back end-editor to latest version.
Check this link. You can see Release Notes there that says VER 5.6 - Update: Compatibility with WordPress 5.0.
So just update your plugin & sure that will fix your problem.
Try it & let me know if you have any issues.
Use the plugin call classic editor. It uses the old editor. Do not use classic editor addon. Just the standard classic editor plugin.
You can use Wordpress Version 4.9.9
It is working for me.
Download link
I can’t find Backend Editor, where is it?
The WordPress admin panel is a very unpredictable environment for such a complex product like Visual Composer. Because of that, we decided to remove Backend Editor in 2.0 version and focus our development on Frontend Editor. As a result, you as a user are getting a more stable and faster editor. Release cycles will become shorter and new features will be delivered to you faster.
To justify the “loss” we will introduce new “structured view” mode in Frontend Editor (similar how it was in the Backend Editor) and there is always Tree View mode available (a layer style representer and editor of your layout).
official website
I have a doubt at this moment.. I'm wondering how to know what is the latest stable version in Github repository of symfony? Any help?
Using symfony new project_name it says it is 2.7.3, but how to know it in Github to fork it?
In GitHub you can look for tags. Only stable realeases are marked by tags with only version in name. Sometimes Symfony have Beta-versions. These versions are marked with tags too but always have appendix: BETA.
So for now the actual stable version is 2.7.4. You can see it in screenshot:
You could check the symfony road map.
http://symfony.com/roadmap
When I try to add a web-service-client from a WSDL, I get an error, and to get past this error I have to delete a file called "javax.xml.soap_1.3.0.v201105210645" from the 'plugins' folder.
Here's an original post:
http://forum.spring.io/forum/spring-projects/springsource-tool-suite/91609-sts-2-5-1-java-io-filenotfoundexception-lib-saaj-jar
Isn't there a way to fix this permanently?
I tried this again with the latest STS 3.6.3 version and it seems to work just fine. The Eclipse bug at https://bugs.eclipse.org/bugs/show_bug.cgi?id=364026 is fixed since quite some time. Please make sure you are using STS on top of the latest Eclipse 4.4 release. The bug in Eclipse Webtools got fixed for Eclipse Luna (4.2), so if you are running STS 3.6.3 on an older Eclipse version, this bug is still there, I would guess. Hope this helps!
I upgrade a Plone site from 4.2 to 4.3. The upgrade steps are basically:
running install.sh to have a 4.3 environment
copy Data.fs to var/filestorage and custom dexterity package to src
running upgrade in ZMI
Everything seems fine. But when I add/edit Page items, TinyMCE toolbar is missing for the body field. Only showing a Text Format dropdown. Note: I do see the toolbar trying to render (first 2 icons appear), but fail and disappear.
What am I missing? Any hints?
No definitive answers, but a few suggestions. I have 9 plone sites all running the same version of Plone (4.2) and have some where TinyMCE works flawlessly, and others where I can't make it work at all.
Check /portal_javascripts and make sure that you have ++resource++plone.app.jquery.js (I think you also need jquery-integration.js and ++resource++plone.app.jquerytools.js, but I may be wrong about those), as well as tiny_mce.js and tiny_mce_init.js).
check /portal_kss and ensure you have ++resource++tinymce.kss/tinymce.kss
check /portal_css for ++resource++tinymce.stylesheets/tinymce.css
I saw your edit about the toolbar beginning to display after I posted this response. You really need to use the development tools for your browser-of-choice (e.g. Firebug) and look at the console. If it starts to display and then fails to finish, there's sure to be an error in the console log.
Check to see whether you have outstanding upgrades to the Products.TinyMCE:TinyMCE profile in Upgrades in portal_setup via the ZMI. If there are any, run them and restart your Plone instance.
I had the same issue with the same version upgrades and there were outstanding upgrades. They must have been missed somehow, presumably a bug in the Plone upgrade process from 4.2.5 to 4.3.4.
FWIW, I just ran into this issue in an upgrade from 4.1 to 4.3.14.
In my case, the problem was that the site uses the Plone Classic skin instead of Sunburst. The Classic skin for some reason did not have the tinymce layer registered. The giveaway was that jquery.tinymce.js was registered in portal_javascripts, but marked in orange as (resource not found or not accessible). I grepped the buildout eggs and realized that jquery.tinymce.js lives in a skin layer of Products.TinyMCE-1.3.26. From there it was easy to figure out why it was not found.
Over the last year or so I tried using WP-CodeBox for a syntax highlighting tool. I downloaded a couple of versions and tried them with a few versions of WordPress. I have never been able to get CodeBox to work. Anyone suggestions? Anyone using this combination or have a similiar story? What did you do?
I like the features it offers like links to download files, line numbering, copy to clipboard, and expand/collapse of the code box. If there is another tool that offers these features, let me know.
WP-CodeBox - http://www.ericbess.com/ericblog/2008/03/03/wp-codebox/
I'd prefer to use CodeBox but if I can't make it work, I need to use something else. I cannot change the version of WordPress.
I've been using it successfully on my blog. I just upgraded to 1.4 which appears to have broken a few things so I downgraded back to 1.3.3. I'm currently using 1.3.3 with WP 2.8.6 & just upgraded to 2.9. Haven't had any problems with the 1.3.3 version. Just noticed on Eric's site that he recently released 1.4.1. Haven't tried it yet though.
lamolabs blog is my blog. I use the WP-Codebox all over the site without any issues.
I use it with WP 2.8.4 in production site and 2.8.6 at home, both working fine.
I've just installed on the same version and it's not working properly. It displays the code, but the collpase bar, images and line numbers don't appear. I'm going to have to hunt around for something else.