I am particularly interested in a how hide folders work or how can it be achieved programatically (.net). How can I create a folder such a way that
its hidden
Does not appear in search (even if hidden folders are opted)
No files system structure modifications are required
How are folders encrypted. Any links or advices would be great. Thanks in advance.
I know you can hide drives using a registry setting:
http://www.pctools.com/guides/registry/detail/148/
but this will not create the invisibility in searches that you want. I know this doesn't really answer your question. However, if nothing else, hopefully it will keep others from going down that road... =p
On the other hand, Truecrypt is open source. I haven't had an interest in this subject myself, so I don't know how it works (beyond the fact that it uses a special storage driver in Windows), but you can check it out for yourself here:
http://www.truecrypt.org/downloads2.php
I expect it's a device driver (maybe a filter driver to the file system).
Without writing a device driver, the easiest way is to use one of the (apparently many) 3rd-party add-ons which implement this functionality.
Related
I am looking for the ability to enhance the appearance of the directory listing pages of a very basic corporate intranet I developed for use by our employees. I am using Windows Server 2012 R2, and the site is deployed in Internet Information Services.
I did not use anything like Visual Studio to create this, and I have already handwritten all of the CSS and HTML for the index page that serves as a jump-off point for the rest of the site so that users can get to the content they need; however, the directory listings pages where the users land leave quite a bit to be desired to say the least.
I just want to be able to add some quick styles to these directories, such as modifying the font family and perhaps the link styles. Nothing major, really. The site already functions perfectly for what it was designed to do, and has been for years. This is just something that's always kind of bugged me but I never devoted any time to it. I'd like to do that now. Ideally I'd be able to just add something in the web.config file like inline CSS, or perhaps link it to a .css file that will house the styles. The latter is probably preferred, actually, but any way is fine.
Any help is greatly appreciated. To get this out of the way early: yes, I have done lots and lots and lots of searching on this topic — I'm talking hours. I have not been able to find a solution that seems to meet my needs. I consider posting here as somewhat of a last resort because I understand that it's a free resource and users here are usually quick to let other users know when they didn't find a particular article that seems to offer the solution they're seeking — which is usually a result of not knowing exactly what keywords to use — and I don't want to waste anyone's time. Just know that I have tried everything I know to find the solution, and that I'm genuinely stumped and looking for help from some pros.
Thank you!
Since the directory page is not HTML, you can't directly style it with CSS. However, there are a few options for changing the way it looks.
Write a script to point to your own, custom-styled, directory page. See this forum thread for tips on how to do that and a sample script.
Create a custom page using this module that you can further customize yourself.
Use the DirectoryListing open source app, which allows for customization of the directory page.
Either one of those solutions should give you more control over how the directory page looks.
I do not have much experience with plone, I searched on other forums an answer to my problem but without success. I saw that with plone you can enter text via "Add" event, news, page, file .... is to add a file that I have encountered a problem, that I can not add more files. I need to add multiple files with a single description, there is a way to do it?
Thank you !
Supposing you are looking for a possibility to batch-upload files into a folder, there are several add-ons for help out there. I live happily with collective.quickupload, but you might want to make your own choice and have a look at the other products, too, as for example:
wildcard.foldercontents (this will be the default behaviour in Plone 5)
ATMassloader
collective.upload
collective.uploadify
PloneFlashUpload
PloneJUpload (Java)
sc.base.uploader
Also: Plone/Zope has a native FTP/WebDAV-support. You can connect to a running Plone using a Webdav client, upload files and see them loaded in the CMS.
Additionally plone.formwidget.multifile allows you to add a file-field to your contenttype, which is capable to select multiple files at once for the upload in one single file-field. Haven't seen an out-of-the-box integration into a contenttype around, though, just in case you'd like to do it :-)
Might be interesting, too in this context:
Browse-able ZIP
collective.archiveviewer
I've been trying to figure out how to make the current SlickUpload 6.1.7 play nice in a form that does not require someone to include files. We want it to be optional. This form is for people to contact us, and we want to give them the option to include attachments, just not require it. It works if you upload a file, however the form will not submit, if you do not upload any file.
We are trying to use the Ajax version with Memory stream, but the 'AspNetAjaxCs-VS2010' sample code is not helping much... the documentation is sparse, and the samples have little constancy between them, making it hard to understand how exactly it all works. (at least for me) The fact that they got bought out, and the new owner company pretty much ignores people unless they are paying for it, is not cool.
Any ideas?
You could use a div to detect a drop inside your page. That way you could only activate it when the user really need it, or whenever the using actually select something for uploading, like a trigger.
I'm not sure I understand your question, but if so, it sounds like you already have a form that you want to use SlickUpload with to upload files IF there are files to be uploaded. Are you using the CustomUploadStreamProvider form?
I've built a complex site for a client, who wants this duplicated, and re-skinned, so it can be used for other means.
What is the best way of doing this? I'm concerned about copying every file as this means any bugs must be fixed twice, and any improvements must be implmented twice.
I'd look to refactor your code.
Move common functions into a library you can reference from both projects. As you mention that the new site is for a different purpose then you are likely to see divergence and you don't want to hamper yourself later, so extract the common parts and then modify copies (or if appropriate new files) of the remainder to complete your fork.
If you haven't applied good practice already then now is the time to do it and it'll make your work on both sites easier moving forward.
If all the functionality is the same and only the layout is different you could just create a new css file. 2 websites could have exactly the same code base but have different stylesheets and look completely different.
I think that using a version control system like subversion or preferably git, is a good way to duplicate your website. You will be able to track the changes that you make and revert to older versions if things do not work out.
You should implement some kind of instantiation, so look and feel, content and data will be shown depending of what instance of the application is accessed.
In other words, each application access to the code with a different application identifier, meaning content will be served depending on it.
Both application identifier will be pointing to different settings, so stylesheet and content will be absolutely isolated, and both domain will be living in the same IIS application.
If you want to duplicate a whole site it's probably best to copy the whole thing and amend as necessary. Obviously taking great care not to copy large portions of text or else you may be penalised by the search engines.
There are ways you could put the new site onto the same shared host (say within a subdirectory of the original site) and literally 'share' some files. If a unique change is required, you could instead reference a 'local' version of a particular file.
However that sounds like a recipe for a headache to me. I'd prefer to duplicate the whole site. It would be much easier to replace one or two functions on separate websites than it would to try and work out which website(s) are affected by a particular change to your source.
I have an ASP.NET website and over time it has become more and more of a data repository where I have numerous database tables and the site just ships out this data.
I am realizing that a wiki might actually start to be a better model for what my website is turning into. Or at least parts of it as it's really just adding and updating content that I am doing. Here is my dilema:
There are certain parts of the site that do need to be non-wiki and fully customizable, etc. Should I go and build my own wiki capapabilities into my website so I can make it part wiki (embedded when I need it) and the rest regular ASP.NET? If the answer if yes, are there any tips or boiler plate code on how to build and host a wiki?
The alternative is to use existing wiki software. I have tried most of them and my issue is that I need to host it myself on Windows and as mentioned above I want to have complete control and have just a simple wiki page editable inside my site. I have tried using frames, etc. to simulate this, but it all seems kind of hacky.
Any advice on:
A. If you think I should build the wiki part of my site below, is there best practice, boiler plate code on how to do this quickly?
B. If you think I shouldn't go reinvent the wheel, is there any existing Windows-hosted software that I can embed in my site without losing any control?
Rolling your own is a waste of time unless you have some major change or addition to the functionality of a wiki not otherwise available in existing systems (and even then, it's often a waste of time to start over than to branch an existing setup).
I recommend using something like ScrewTurn, which is open-source and ASP.NET, which gives you a fully-functioning wiki with no development, as well as gives you as much control as necessary if you do need to make changes.
I would agree with Rex M. You don't need to start from scratch. Leverage an open source product that is already available and build on it (if you even need too).
The added benefit of that is from a collaborative perspective when you build some interesting functionality into your version of the software and then share that back with the community.
Chances are if you need to build something and find it useful that other folks somewhere have close to the same needs and would welcome your features and enhancements.
That's the beauty of open source.
Take a look at dooWikis. With this, you can embed wikis into your site like you want to, without redirecting to a third-party service, and restrict who gets to make edits.