I built a site using blogdown in Rstudio. I'm not sure if I am experiencing a bug or if this is expected, but it is kind of annoying, and I'm wondering if I can fix it.
When I use
serve_site()
All of the old file folders I deleted come back in my public folder.
My current set up is with the Lithium theme, and I make several test documents and folders to test the linking. When I make .Rmd files in the content folder in particular, it will create a folder with that name in the Public folder as well as that name_files.
After I delete the test folders and test file folders, the test file folders come back after I use the serve_site() function in Rstudio.
Example:
1) Add "Example.Rmd" to the content folder
2) Automatically an "Example" folder is added to the Public folder with the index.html
3) Automatically an "Example_files" folder is added to the Public folder with the related files
4) After testing I delete the Example.Rmd, Example Folder from the public folder, Example_files folder from Public
5) After using serve_site() in Rstudio, the "Example_files" folder comes back - I cannot delete it!
Thanks again
Look for *_files directories under the static/ directory (under your website's root directory) and delete them there.
Related
I'm git newbie and developing using Xcode.
As I mentioned in title, the file path shown different between IDE and working directory.
The file path that Xcode shows me is:
MyApp/FolderB/Model/DummyModel.swift
However, in the working directory shows me is:
MyApp/FolderA/Model/DummyModel.swift
The remote repository has the same file path as the working directory.
HISTORY
At first, I created FolderA, which included Model folder and DummyModel.swift.
Later, I created FolderB and moved the Model folder hear. And deleted FolderA. I think I modified DummyModel.swift after moved it, but I don't remember clearly.
Why did this problem occur?
What should I study to understand this problem?
I'm new to Ruby and Jekyll, and I've been following this tutorial on how to create a static-site. I've reached the part where we're supposed to edit files inside the _includes and _layouts folders, but those folders don't appear in my directory. There is however a _site folder with an index.html file inside it, and it looks like that's what's showing when I run the website with 'jekyll serve'. Am I supposed to add these folders and files in myself, or should I edit _site/about/index.html to match what the tutorial has?
Here's a picture of what my current folder structure looks like:
Yes, you should add those folders and files yourself. Copy them from the theme repo and skip anyone you don't want to customize / override. The default theme config created by command jekyll new is https://github.com/jekyll/minima
The _site folder is being generated on the fly, it reflects the result of the customization.
I want to access to a directory of an xcode project that contains cocoapods (firebase framework) in my Desktop! But I keep getting: No such file or directory!
I tried to access to another non-project folder and it worked.
It also worked when I tried to access to a project folder that does not contain cocoapods!
I don't know why I could not access to any project folder that contains cocoapods!
When I list the contents of the desktop I got:
There is an # in the properties
What does that means and how can I access to the folder?
I just want to upload it to the Github? any solutions?
BusinessWallet is probably a framework bundle, which means that it is actually just one file, but appears as a directory in Finder. You can copy individual files out of it in Finder.
If you need programmatic access to contents inside the bundle, take a look here: https://developer.apple.com/library/mac/documentation/CoreFoundation/Conceptual/CFBundles/AccessingaBundlesContents/AccessingaBundlesContents.html
I have created a new version of my Joomla extension.
Manual upgrade via zip file or the directory works fine.
But the automatic upgrade (which used to work fine before), now gives an error 500 and the following error messages: "Unknown Archive type", "*Update path does not exist" and "Installation unexpectedly terminated: Update path does not exist".
I have no idea why those messages appear.
The update.xml references the correct zip files. Downloading it manually works just fine.
Joomla(/php/apache) has all rights on the folder containing the joomla installation.
After trying the automatic update, the tmp folder contains the downloaded zip archive with the latest extension version, interestingly without the .zip extension. Is the Joomla downloader not correctly naming the file and then failing upon finding that the file doesn't have a .zip extension?`Or what could it be?
Would be very thankful for any ideas...
Edit: My project is hosted on github, and github seems to automatically create a subfolder in the downloaded zip archive, named -.zip.
I'm using a link to the tagged github zip directly in my update.xml
I'm not sure if github always added this folder in the zip file, back when it still worked for me...
Might the Joomla problem have to do with the zip file containng such a folder, and not directly the extension stuff at root level? If so, anybody know if/how I can change github to not create that subfolder?
Right, just had a quick test of this.
I couldn't seem to find out how to automatically zip up a sub folder (there is a way but I need to do some more research/ask questions regarding this), however what you can do is the following:
Create a zip of your Repo
Open the zip, extract the folder you wish to be zipped then zip it
Create a new version and then drag your zip file into the upload box
Publish the release
Here is an example, have a look at the "Creating Releases" sections at the bottom:
https://github.com/blog/1547-release-your-software
Hope this helps
To answer my own question:
Yes, github seems to have recently changed their policy to create a root folder in the zip file, named as the repository the zip file is downloaded for (stupid, if you ask me, since the exact same information is encoded in the zip file name already anyway!).
Edit and Rewrite: It seems that either something changed in Joomla or that if you adhere to a naming convention - namely the root folder in the zip file having the exact extension name (or, I think and have to test, actually the same as the file name, without the version information), then the automatic update will work.
So as in my case, I have a Joomla package; the package is now in a repository pkg_mypkg. The zip file generated by github has the name pkg_mypkg-version.zip (e.g. pkg_myfancyext-1.0.9.zip), and contains a folder named pkg_mypkg. And inside the pkg_mypkg folder is a pkg_mypkg.xml file, the extension manifest. And this actually seems to be the configuration where automatic update works.
My installer has been working until a few days ago, now I get:
JInstaller::install: File '/home/john/public_html/tmp/install_4c578c96e449f/com_mycomponent/admin/site/controllers' does not exist.
I checked the zip file and everything looks ok, I changed file contents but not the file structure at all since the time it was working.
ZIP STRUCTURE
com_mycomponent.xml
admin
controllers
...rest of admin files
site
controllers
...rest of site files
In fact the folder
com_mycomponent/admin/site/controllers does in face not exist, I don't know why it is looking for this folder.
Please check your templateDetails.xml file. It must have mentioned about the folder name. Also, make sure if you want to add folder through template then that folder must not be empty
I had the trouble that I had accidentally put a copy of the xml file inside the admin/ folder in addition to in the root folder. Maybe this happened to you too? Just delete it and it works fine!
If you have any backup files on the components folder or some where in the project folder delete it or cut it to some where else...
May be that solves your problem.
Because that solves for me.
thanks
I had the same problem. One of the file names, in templateDetails.xml had a typo. That solved my issue.
For some reason it did not like my HTML file, so I deleted it from the XML. When I checked the module installed and the HTML file was present. I still included <folder>html</folder and also <filename>index.html</filename>