This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi Guys, I have a peculiar problem with Workbench, which we've just started using in our project. When Im working with scss files and Im saving them in order to generate appropriate css, it only works if scss file does not contain any @import statemets. In other case, Im receiving the following error: Syntax error: File to import not found or unreadable: colorSpecifications. Load paths: C:/Windows/System32 C:/Work/OneABB-WCMS/trunk/Projects/Abb.Portal.Web/AppData/Sitefinity/WebsiteTemplates/AbbBranding/AppThemes/Yellow/Global on line 1 of C:\Work\OneABB-WCMS\trunk\Projects\Abb.Portal.Web\AppData\Sitefinity\WebsiteTemplates\AbbBranding\AppThemes\Yellow\Global\yellow.scss Use --trace for backtrace. The resulting css file contains the same error instead of styles, therefore its not usable. The second load path (C:/Work/OneABB-WCMS...) is the directory which contains the file which I was editing. The file which Im trying to import is called colorSpecifications.scss and its located in the application root folder (next to web.config) and we want to use the variables from that file in many on our css files which are located in our AppThemes folders. The first path is a mystery, sometimes it points to system folder, other times it points to one of VS2010 directories (for example: Any ideas how to resolve this issue, and what may be causing it? It appears for some of my team mates but not for all, and we are all using the same Workbench version (the latest) best regards Pawel |
|
|
Hi Pawel, Can you add:
as the very first line to your .scss file and then copy in the resulting output in the output window after re-saving.
|
|
|
Hi, I'm also a developer from this team. This is the trace output:
As you can see the second path is always from the scss file that we want to compile on ctrl+s The first path however... We cannot figure out where it comes from. Now it is "C:/Work/WCMS/trunk", it can also be "C:/Work/WCMS/trunk/Projects", or "C:\Windows\System32\" etc. Maybe it would be nice if the Workbench just had additional searching path to be the root of the sln. |
|
|
Thanks for the additional detail - the first path will be the working directory from Visual Studio at the time the tool is run but all paths will be being used so that is not a problem in terms of locating the file. Ive tried setting up a quick example using your folder structure here with two files under the Blue folder: blue.scss (uses the mixin) and colorSpecifications.scss (declares the mixin) and this is working fine for me, you mentioned that this does work for some of your developers but not for others?
|
|
|
Ah, I just re-read the original post - is colorSpecifications in the Blue/Yellow folder or the root of the web application? If its the latter this will not work. The import statement needs to be a relative path against the importing file. e.g. For the Blue example it would be
or if you are using a consistent folder structure you can specify the load paths manually using the following directive (a reminder this needs to be the first line of the file)
|
|
|
Thank you very much, The absolute path option worked for us (although then enabling Include debug info did not work, you had to set the parameter manually), but since the not all developers have the same path we changed to the relative version and it worked for us as well now. We tried relative solution before but the error message did not indicate which directory it was searching in, only those two paths which were always the same, so we thought it is not working. Anyway thank you for support |
|
|
Hi Jeremy, In relation to our discussion from October 2012, I have a problem which started once I installed the latest Mindscape Workbench release through Nuget yesterday. It seems that generation of css files which are not in the same directory as scss files stopped working - there are no error messages but the files are simply not regenerating. There were no changes from our side regarding the configuration since Oct 2012, so the paths are all the same etc ... except that were using VS2012 now. Did you guys make any changes in this particular functionality? FYI, it still works fine for the css files which are in the same directory as scss file. best regards Pawel |
|
|
Hi Pawel, We have had a similar bug reported and so the fix associated with this will be pushed out with the next gallery update which will be this week - if you can retry with that version and let me know if its still a problem.
|
|
|
Hello Jeremy, I just installed the latest version through Nuget today, and it seems to have fixed the problem only partially. After I edit the .scss file only one or two css files (out of nine which is supposed to be affected) is actually regenerated. What I've observed today is that it happens pretty much randomly (once its blue.css, other times yellow.css, other times blue.css and bluegreen.css) .. so it seems that the problem is not entirely fixed. best regards Pawel |
|
|
Hi Pawel, Thanks for the update - are you able to send us through a small repro project which exhibits this behaviour please (the content of the files should be largely irrelevant other than for linking them and verifying that something is being correctly included) and I can have a look at getting out an additional fix for this.
|
|
|
Hi Jeremy, Today I have retested this a couple of times and it seems to we working fine now. Perhaps on friday it was just an issue of my IDE longing for the weekend ;) .. although I've been restarting it etc. Anyway, I'll keep an eye on this and will let you know if anything weird happens. Thanks for your help so far! best regards Pawel |
|