Running into a problem where normal pages are working fine, however collection pages are not found by html-proofer.
Example error message:
* internally linking to /blog/choose-a-datasource, which does not exist (line 82)
Choose a data source
This message comes from the following Travis report. There are a lot of collection pages not found:
https://travis-ci.org/semi-technologies/semi-website/builds/514826595#L1065
However, when you look in the source folder the the page does exist:
https://github.com/semi-technologies/semi-website/tree/permalinks/_blog
And in a jekyll build these files are successfully created in ./_site.
Does someone have experience with this?
Related
I fail to understand some options in the dumpBackup.php maintenance script of Mediawiki.
What is the effect of --include-files? In my test wiki, dumpBackup.php --current --include-files and dumpBackup.php --current both contain the pages of the File: namespace and I see no difference.
What is the effect of --uploads? In my test wiki I see that the xml file contains a tiny bit more of xml but, to me, it looks like this is all information which is there already as part of the File: page. What is the use of this flag?
When I add both --include-files and --uploads I get the next surprise. I actually expected the combined effect of both options, but what I get is the file content of the uploaded files and the upload record. Why did I not get the file contents when I used --include-files alone?
When I use only --include-files and --uploads but no --current I would have expected to get the content of the uploaded files and the upload record (and none of the other pages). However ,I get the warning no valid action specified and no further information at all
I am completely confused since I do not understand the logic behind all of this.
basically opening this question again because the answer is outdated, as the link now redirects to Firebase:
Gradle fails building with "Missing project_info object"
I want to attach the google-services.json file to my Android Studio project, and every time I try to download it from the developers API from Google, it gives me a json file with a large name that does't correspond to the tutorial's simple "google-services" and renaming it won't work because of this error.
Downloading it creating a new project doesn't seem possible for me now as it the page gives me another error when I click Configure a Project (I already did that before but left the project there without downloading the json file directly from there, which seems to be the problem).
Where can I safely get this file, and should I rename it or? Thanks in advance.
Apparently the solution is just following the link and creating the project with Firebase:
Then create or select a project and fill it with your app data that shoul look like this (the SHA-1 key should be found in your console log when clicking the button in the image:
Then add the lines of code that should be in your build.gradle(app level one and project level one), editing them with notepadd. Finally you need to sync these Gradle files, in Android Studio : File->Sync project with Gradle Files
The tutorial is very self explatanory, but for beginners like me, this could help.
I notice my files in polymer.json/fragments are not copied over to my build/bundled folder. This causes 404 errors, how can I resolve this?
Strangely they are copied for the unbundled folder ...
Seems like this is usually because there is some error in polymer.json. For example, when trying to include a file that does not exist. Unfortunately, Polymer does not fail with an error; it succeed with weird results ...
I'm using BO XI 3 and wanted to know if is possible to open an InfoView folder using an OpenDocument link?
For example, every item in InfoView has a CUID. So to open a web intelligence report I could do the following:
http://Server_name:6060/OpenDocument/opendoc/openDocument.jsp?iDocID=ABCDEFGHIJKLMNOPQRST&sIDType=CUID
Folders in InfoView also have a CUID, so is it possible to link to them using this method to take a user straight into the folder? Whenever I try I get an error message (An error has occurred: An error occurred while trying to view the document), is there a way around this?
I'm guessing the answer will be "OpenDocument is for opening documents, not folders". Thought I'd ask anyway...
I don't believe so, for this reason: the openDocument.jsp/.aspx command is really just running an object, so it's expecting either a report object, or an instance (in .rpt .pdf .rtf .xls, etc) that it can either render or open in another application. Although a folder is a legitimate object w/ a CUID, it isn't something you "run/view" - rather it is something you browse.
Cheers!
Stefan
http://www.sdn.sap.com/irj/boc/index?rid=/webcontent/uuid/5001d5de-f867-2b10-00bf-8d27683c85a0#section5
Trying to build a CHM using Microsoft HTML Help Workshop. A soon as I click Compile, HTML Help Workshop states:
An internal error has occurred. An error record has been saved to c:\os.err.
The only contents of the file are:
((Today's Date & Time))
Microsoft HTML Help Workshop Version 4.74.8702
HHA Version 4.74.8702
htmlproc.cpp(114) : Assertion failure: (pszTmp == m_pCompiler->m_pHtmlMem->psz)
The error only occurs for a few select, large projects, and happens from both the command line as well as the HTML Help Workshop GUI.
What causes this error to occur and how can I fix my project to run through the compiler?
The Microsoft HTML Help compiler has some unstated requirements for path name sizes.
Moving the project to a directory closer to the root drive (i.e. "C:\helpsystem\") and renaming folders inside the project to smaller name reduced the path name size enough so that the project would compile.
I found Microsoft HTML Help Workshop to be a bit delicate to work with. Do you have all the prerequistes installed? Try running the compiler, hhc.exe, from the command line.
Another thing to watch out for is an Error 413 - Request Entity Too Large error.
I'm not sure how big is too big for HTML Help Workshop, but my htm file is a touch over 2MB, a large table, and it causes HTML Help Workshop to crash when processing it.
While this isn't the same problem, it was the hint I needed - I'm not the first to find this on SO..