Having Nikola ignore certain files - nikola

So basically all I want is to add data to my Nikola post folder (CSV, KML, ESRI Shapefiles, JSON, XML...), my posts are written in Jupyter notebooks so naturally need to reference data for writing posts and I would like for those who view the blog to access to data to replicate the results (though I'm flexible on that point). For a while I was able to place extra folders and CSV files in the post folder without Nikola throwing a fuss that those are not a post. But now when I add new files to the posts folder and run nikola build it throws an error, so I may have either forgotten the method I used the first time or messed something up along the way.
Here's the error:
Scanning posts....[2017-12-16T01:18:56Z] ERROR: Nikola: Missing date in
file posts/SnowGIS_SHP/README.txt
[2017-12-16T01:18:56Z] ERROR: scan_posts: Error reading post
posts/SnowGIS_SHP/README.txt
[2017-12-16T01:18:56Z] ERROR: Nikola: Error reading timeline
[2017-12-16T01:18:56Z] ERROR: Nikola: Error loading tasks. An unhandled exception occurred.
[2017-12-16T01:18:56Z] ERROR: Nikola: ValueError: Missing date in file posts/SnowGIS_SHP/README.txt
[2017-12-16T01:18:56Z] NOTICE: Nikola: To see more details, run Nikola in debug mode (set environment variable NIKOLA_DEBUG=1)

I'm so silly, basically all I had to do was remove the README.txt file.

Related

File not downloading laravel 5.6

I've read other questions and implemented answers but haven't had any success.
Here's the error:
files in database, and locally:
here's my form:
here's my file-controller:
The flow is I upload a file, it is stored into the database, and locally, the files locally work properly. I implemented the download attribute and was able to get actual files, but those files and that process was scrapped because the files downloaded, while they had the correct names and mime types, the file had a error like "could not open file".
I am primarily using the download method in the filecontroller which you can see above, I used some ideas for getting the actual path to the file, as that seems to be the issue, but even using the storage_path method I'm getting this error.
Thanks!
I didn't understand the pathing for filestorage enough, and was therefor obviously getting the incorrect paths to the file being stored.
For example, the storage_path method returns the path to storage, I thought it was going to give me the exact path to the file. Once figuring this out I was able to navigate and fix my issues.
filecontroller
line 52: storeAs was storing to a redundant path, i made it as '/upload'/
filescontroller#download
return response()->download(storage_path("app/upload/{$file}"));
following the paths where files were being saved locally, I was able to fix this issue.

How to get more specific debug messages and warnings from Aurelia

After making some coding changes in my project and refreshing the page, I encountered the error below:
This tells me that the file loan.js could not be found. My first thought, then, is to find out what file is trying to make a call to loan.js. When I expand any of those errors to view the stack trace, I see system files like:
system.src.js:xxx
aurelia-loader-default.js:xxx
aurelia-templating.js:xxx
compose.js:xxx
etc
What does not show up is any specific file that would lead me to where my error is. It turns out that in myFile.js
I had forgotten to provide the specific path to loan.js
view-model="loans/loan"
With multiple view models and views where we make references like the above, how are we expected to debug issues like this when the communication is not specific? Is there some debug, logging error options that I am missing? I'm used to compilers at least providing the last place where the file was attempted to be fetched (causing the 404).

Fatal error: Class 'Mage_Sales_Model_Order' not found in ....core/Mage/Reports/Model/Resource/Order/Collection.php on line 456

I was installing magento 1.9.1 on my server everything went fine but after installation when i click on Go to Backend and give my username and password to login to Admin Panel it gives the following error:
Fatal error: Class 'Mage_Sales_Model_Order' not found in
/home2/siatel/public_html/4ebay/app/code/core/Mage/Reports/Model/Resource/Order/Collection.php
on line 456
Though my frontend side of website is working perfectly ... Please help.
I can see my admin log-in page. Error comes only when I give username and pass and hit continue...
Without more information, it sounds like you're missing your
app/code/core/Mage/Sales/Model/Order.php
file. It seems like you're missing a lot of different files as well. I'd diff your installation vs. the contents of a standard tar archive.
Your error shows like this
Fatal error: Class 'Mage_Shipping_Helper_Data' not found in
/home2/siatel/public_html/4ebay/app/Mage.php on line 547
see the portion 'Mage_Shipping_Helper_Data' not found. It means Magento is looking for a helper class file and it couldnt find it. Magento will look for this file in app/code/core/Mage/Shipping/Helper/Data.php.
I will give you some hint on how this file path came from. First of all magento core files lies in the location app/code/core/. Then missing class name (in this case Mage_Shipping_Helper_Data) will converted as Mage/Shipping/Helper/Data.php. Then this will append to the core codePool directory path. That is app/code/core/Mage/Shipping/Helper/Data.php
For every file, magento assigns path as like this. Please note that, you need to attach .php part to the last keyword. Also you need to copy the exact same data of that file (take into consider the version). It means it need to have a 'Magento way' class name and so on

Breeze JSON Parse Error for Metadata

I just upgraded my Breeze nuget package from 1.1.3 to 1.2.7. I was getting error about some of my classes that had "ComplexType" items, so after upgrade I am getting the error below when reading the Metadata from my MVC4 Web API. Everything was working properly before that with the exception of ComplexType, so I know for sure everything is in place, since I was getting the Metadata, and was able to show the data on the screen.
Uncaught SyntaxError: Unexpected token o
Uncaught SyntaxError: Unexpected token o breeze.debug.js:12561
ctor.fetchMetadata.ajaxImpl.ajax.success breeze.debug.js:12561
jQuery.Callbacks.fire jquery-1.9.1.js:1037
jQuery.Callbacks.self.fireWith jquery-1.9.1.js:1148
done jquery-1.9.1.js:8074
jQuery.ajaxTransport.send.callback
I was having the exact same problem and I noticed that when you issue a GET against the metadata location (/api/Context/Metadata), it returned an xml document formatted as json. I also think there is a related question, but in a slightly different context. In this case however, the error was raised at ctor.prototype.fetchMetadata in a line containing JSON.parse(). But I'm pretty sure is the exact same underlying cause.
Just update Breeze from Nuget (both the the dll and the js files) and that would do the trick.
Notice that you might have to manually delete the breeze files from the /Scripts folders.

NSURLErrorDomain error -3001

I'm trying to download a file from the internet, but I get the error -3001 back. I've been searching through google but the error doesn't appear on any website, so i have no idea what it means.
Can anyone tell me what the error code "NSURLErrorDomain error -3001" means?
Thanks
There's also a full list of all NSURL error codes here. It's very handy when you get cryptic error messages from the URL loading system.
I wrote an applescript awhile back that can search the header files for error codes. You can find the applescript here.
I ran that applescript for your error code and got this from the CFNetworkError.h file.
Error Description:
kCFURLErrorCannotOpenFile
The error comes from the fact that setDestination expects a full path with a filename:
This is wrong:
[fileDl setDestination:#"/Users/ant/ebooks/" allowOverwrite:YES];
This is right:
[fileDl setDestination:#"/Users/ant/ebooks/file.epub" allowOverwrite:YES];
So the explanation is that probably you did something like I did: specify an existing folder where you intended to put the data.
PS: the dash before 3001 prevents Google from returning any results with the request: "NSURLErrorDomain error -3001", it is parsed as: "NSURLErrorDomain and error and not 3001"..

Resources