I am using Symfony2.3 _ Sonata Admin + Sonata E-commerce Bundle All installation is successfully done.
But When I go Back-end url as login then show me :
An exception has been thrown during the rendering of a template ("[ERROR 522] Validation failed: no DTD found ! (in n/a - line 2, column 21)
[ERROR 1877] Element '{urn:oasis:names:tc:xliff:document:1.2}trans-unit': Duplicate key- sequence ['sonata.invoice.references.date'] in key identity-constraint '{urn:oasis:names:tc:xliff:document:1.2}K_unit_id'. (in /var/www/xyz.com/web/ - line 172, column 0)") in SonataUserBundle:Admin:Security/login.html.twig at line 14.
I don't know why ?
I am totally confuse?
Any one know this ?
Indeed, this has been fixed here: https://github.com/sonata-project/ecommerce/commit/1aee2f8f78eb38a42b5f84260348262af8c2312d#diff-d0af37f82ac64ab8fc32c34c2f39b110
You should update your dependencies to fix the problem. Thank you.
You have probably duplicated translation key in your translation file. Symfony can't create translation cache files.
Related
I keep getting this same error from bugsnag for my site, and I'm unsure how to fix it/why it's popping up in the first place.
User Warning · The following theme is missing from the file system: <em class="placeholder">Theme_Name</em>. For information about how to fix this, see the documentation page.
The theme that it claims it is missing is the only theme I have for the site and is the one it is currently using. Besides overloading my bugsnag reporting, it's not causing any issues. Is there a way to resolve this? I checked the documentation page and all the articles I found only refer to modules.
It's likely that the there is an old reference of Theme_Name in the systems table of your database.
You can look for the references that your Drupal instance is checking against by running this query:
SELECT name, status, filename FROM system WHERE type = 'theme' AND name = 'Theme_Name';
Find the reference that doesn't look quite right, preferably by the name of "Theme_Name", and delete it.
DELETE FROM system WHERE type = 'theme' AND name = 'Theme_Name' AND status = 0 AND filename = 'path/to/Theme_Name.info' LIMIT 1;
Once deleted, flush your Drupal caches.
Well this is embarrassing. The source of the problem was that I was adding an image using:
src="<?= drupal_get_path('theme','Theme_Name'); ?>/sites/all/themes/theme_name/img/image.png">
The first problem is that the theme name I was calling was using capitals when the actual theme was all in lower case. But to actually resolve the problem I changed the image call to:
src="<?= drupal_get_path('theme',$GLOBALS['theme']); ?>/img/image.png">
Unsure if this turns out to be the same problem others have had, but that's what fixed it for me. If you're getting this error I'd suggest double checking how your src's are being called. Thanks to everyone that answered/responded!
I am new to symfony.While going through an error template I came across value a value like
#Twig/Exception/traces_text.html.twig
Just wanted to know where is #Twig defined in symfony framework
Just google twig traces_text.html.twig and you'll see the file here: https://github.com/symfony/twig-bundle/blob/master/Resources/views/Exception/traces_text.html.twig
symfony/twig-bundle/Resources/views/Exception/traces_text.html.twig
Or use your IDE and search the vendor/ folder for the traces_text.html.twig file until you find it.
I finished configuring SonataMediaBundle successfully then the page
/formation/web/app_dev.php/admin/dashboard
is displayed.
But when I click "list" (menu Media), I get this error:
An exception has been thrown during the rendering of a template
("Parameter "id" for route "admin_sonata_media_media_edit" must match
"[^/]++" ("" given) to generate a corresponding URL.") in
SonataMediaBundle:MediaAdmin:list_custom.html.twig at line 17.
Any ideas?
I think your problem is based on this known issue:
Sonata type model - hide/delete the "create" button · Issue #530 · sonata-project/SonataAdminBundle
It is recommended to update to Doctrine 2.4
We are transforming PHP Application to Symfony2 Application.
Most of the pages we are completely writing new but some pages we decided to keep it as it is. i.e I want to use the same php without any major change.
In the php page we used GET['prospect_id'], GET['executive_id'] and many other arguments. Both GET and Post methods. When I view the page in Symfony1.4 there is no error or warning.
But when I view in Symfony 2 I am getting undefined index error.
How can I solve the issue?
EDIT: if GET['prospect_id'] is null there is no error in Symfony 1.4 but i'm getting undefined index notice in Symfony2. There are many variables like that. Is it necessary to define variable before use it. How to avoid this notice message.
What i want is if i am using $_GET['xxx']. symfony2 should not show any notice or error. i want to escape from that.
Use (in Symfony2) the controllers request-object, to get those params:
$this->request->get('prospect_id');
$this->request->get('executive_id');
You can also set default values, if there is no value given. Take a look at this documentation.
I am getting strange problem.
When I am listing some content type, intead of data I am getting 'n/a' string.
I listed views, and on one view I have 'Warning - Broken view!' message.
I can't edit / delete this view because it always redirect to front page.
I checked my logs and all I see is repeating:
# warning: Invalid argument supplied for foreach() in /home/www/testetelgsm/www/includes/common.inc on line 3364.
# warning: Invalid argument supplied for foreach() in /home/www/testetelgsm/www/modules/cck/content.module on line 1284.
# warning: array_keys() [function.array-keys]: The first argument should be an array in /home/www/testetelgsm/www/includes/common.inc on line 3361.
How can I delete / edit this view?
Could somebody help?
Regards
You need to go to the views admin page at: admin/build/views. Here you can find a list of all your views and edit/delete them.
It sounds like you are trying to pull something that doesn't exist anymore like a deleted cck field. Anyways, if it doesn't work to edit it, try to recreate it.
You can make views into features with the features module. That will define the views in a custom module that is generated for you, and make the view defined in code. That will make it possible to restore it, if it gets edited.