Just moved a symfony project from local (win) to server (linux), and the icons in the web debug toolbar have disappeared. Only the image alts remain so I guess it's a path issue with the images. Basically, I see "Time 300ms" instead of "[icon] 300ms" for each of the items.
I'm a little worried that some other paths aren't broken as well that are going to be a pain to find.
Has anyone had/resolved this issue?
Thank you.
Solved...
It's a missing alias, but copying this folder in its entirety:
/lib/vendor/symfony/data/web/sf/
to...
/web/
... fixes the paths for the toolbar as a quick solution.
A better solution is to define an alias in your httpd.conf (or whatever the name of your apache conf)
Related
So I just downloaded the open-source QtCreator and I hoped to set the Dracula theme for this IDE, but I failed to do so, and I have no clue what I'm doing wrong.
So far, every where I looked for third party themes, they've been telling me to put it in a map on location "$HOME.config\QtProject\qtcreator\styles" (windows). Fine, but after I've copied the file into that folder, the theme is not showing up in the theme list when I'm trying to set a new theme in QtCreator, selecting Tools > Options > Text Editor > Theme-button :/
I'm quite (90%) sure the path/location is correct, but I assume the themes have moved to somewhere else. I would like to set-up this theme, instead of the default dark-theme. Thanks in advance!
So I found out the themes were located in PathToQt\Qt\Tools\QtCreator\share\qtcreator\styles. The developpers must have changed moved the theme folder, but now between the other .xml files, the Dracula.xml file works just fine.
I hope I fixed every one else's problem, who came to ask himself where the heck they had to put that theme.
I am trying to build my own version of Firefox with slight UI changes and by adding some addons(extensions) to the build.
I have downloaded the source code from repo. Where would I start to achieve this?
Which all codes hold the UI structuring? Where do I put my addon xpi files?
PS: I tried to read the Mozilla documentation. Its either kinda outdated or I am not really getting it? A detailed insight would be much appreciated.
Addons
To do this, simply place the extensions in the distribution/extensions
directory in the application's distribution directory.
Here are the extension
https://dxr.mozilla.org/aviary101branch/source/browser/extensions
Flags In firefox
https://dxr.mozilla.org/aviary101branch/source/browser/config/mozconfig
Do more with themes
https://dxr.mozilla.org/aviary101branch/source/themes/modern
https://dxr.mozilla.org/aviary101branch/source/browser/themes
For Editing you may need XUL
https://www.xul.fr/tutorial/
Components
Go here and customize every component you need
https://dxr.mozilla.org/aviary101branch/source/browser/components
I'm working on Magento installation that is causing me frustration.
I CAN find what seems to be the correct page.xml file loading the theme's Javascript (i.e prototype, scriptaculous, etc) in the header, but editing this file and removing scripts does not do ANYTHING for me. When I try and remove/add any new scripts, nothing happens.
Maybe a cache issue? But I have deleted all files from the cache folder. I also tried to find the "Cache Management" menu in Admin, but there is not one there.
I'm 99% confident that I have looked in all of the folders that would call all Javascript.
I am new to Magento, so maybe I've missed something completely.
Any suggestions on where I could find where the basic scripts would be loading from?
I do not know if I got it right. But what you want to know is the directory where the file .js is located, correct?
Try looking in: yourdomain/skin/frontend/yourtheme/default/js/
or: yourdomain/skin/frontend/default/yourtheme/js/
Page.xml is the correct file you need to modify. If not a caching issue, the only other thing I can think of is you have a theme installed but trying to modify the default(base) page.xml.
This is my first time working with Magento and here is what happend: I spent two days reading the documentation and tweaking the settings to fit my needs. I then installed this theme:
http://themeforest.net/item/decostore-magento-theme/1876494?WT.ac=category_thumb&WT.seg_1=category_thumb&WT.z_author=8theme
The problem is that the theme didn't work the way I was expecting and now I'd like to rollback to the default theme and completely remove everything added by this theme to my installation.
Unfortunately, I didn't backup the installation and database before I installed the new theme and I have no idea where to start.
Thanks in advance.
1. Switching back to default theme
Go to the admin area and then system > configuration > design
Change "Current Package Name" to 'default' and make sure all inputs under the "Themes" section are empty. This will return you to the default theme.
2. Completely remove everything added by this theme
I take it from your question that you are not using any form of source control. Might be an idea to look into this for the future :)
Magento 1.7 has introduced backup and rollback features so you may also want to check that out.
If this is the case, backup everything before you start removing files and directories as described below
Anyway, to completely remove all files and directories added when you installed the module, unfortunately it will simply be a case of manually finding the files and directories deleting.
The easiest way to do this will be to find the original source code you received when you purchased the theme and removing the corresponding files from your site. When removing directories be careful to only remove those specific to the theme - It will have been sent to you structured so that you can easily drag straight in to your web root - so will contain some other directories required by Magento, simply to give it the correct hierarchy.
At the very least there will be files and folders specific to the theme located in the following directories:
app/design/frontend
skin/frontend
js
and also most likely some more in the following:
app/etc/modules
app/design/adminhtml
app/locale
I know the result for this can be different for everyone, but in case someone else comes across my specific case, it was the N98 folder under app/code/community/N98 that caused the problem. Particularly their CustomerGroupCheckout plugin as shown here: https://github.com/amenk/N98_CustomerGroupCheckout
Removing the N98 folder brought back the configuration page.
I am using R#6 and when I edit some razor views, R#6 suggests that I "use directory".
(Whine :)) I dont want to! How do I turn off this annoyance? I have searched through R#6 options. It is definitely R# since the annoyance goes away when i suspend R#.
In the printscreen, R# wants to change /SignUp to ../Signup.
It is incorrect because the view is the layout and could be in any directory structure. So i want it to be /Signup
Solution: As derigel states.
Wait for the warning to show. Hit escape. Then CTRL+Enter. A mini menu appears where you can suppress or change the warning severity. I changed the warning severity to "do not show"
Valamas, OffBySome gave you really good advice, but you still able to disable this warning locally by comment or generally, at all. It's some UI problem here - first, press escape to disable popup, and then, press alt+enter and you will bring few options how to disable this warning.
For your url's, try using relative urls by using #Url.Content("~/images/image.jpg") and #Url.Action("Action", "Controller") instead of hard-coding the absolute / urls. I think this will resolve the Resharper issue, and also make your url's relative in case you are hosting this as a subsite on an IIS instance.
I solved it by properly entering the path.
Original
<Image Source="Images\Q_hor_pos_full_rgb.gif" Height="76" Margin="6,-3,0,7" HorizontalAlignment="Left"/>
It turns out that I had placed this xaml file in a subfolder, and that the Images folder was actually one level higher:
Main\Images\Q_hor_pos_full_rgb.gif
Main\UserControls\File.xaml
Fixed
<Image Source="..\Images\Q_hor_pos_full_rgb.gif" Height="76" Margin="6,-3,0,7" HorizontalAlignment="Left"/>
As soon as I did that, the application found the file with no problem.