I am working in Jobs website using Drupal 6, and I need a button to prompt new users to create their profile pages.
Is there a built-in way to detect if the user has created a profile?
Thank you
The Rules module is what you're looking for. In fact, it comes with that exact rule you're looking for when you install it.
Related
I'm new to web development, and I'm currently making a presentation website(home, services, news, vacancies) for a small company. I'm using Node.js,Express and MongoDB.
The client wants to manage certain content on the website, therefore there needs to be a dashboard, where only admins could login/register. But website design does not provide any login/registration system for users.
The question is, where do I put a dashboard and how should I hide it from ordinary users? Should I just use url, like mysite.com/admin, which should be typed by the admin, whenever he wants to get to the admin login/dashboard zone(it seems quite unsafe, since everybody on the internet could type that and get to the login form)? Or maybe I should make a separate desktop app for managing website content?
How should I approach this problem, what are the best practices?
Thanks!
You don't need to reinvent the wheel as i think you can first explore CMS systems and check if the tools covers your requirement . Since CMS tools brings in lot of website admin capabilities as out of the box features.
Following links will get you started.
https://en.wikipedia.org/wiki/Content_management_system
https://en.wikipedia.org/wiki/Web_content_management_system
I want the user to be prompted with different options, but instead of text, I want them to be pictures, so the user would be able to click the image he/she wants.
I'm working with Microsoft bot framework in node.js.
My question is similar to this but with node instead of C#.
I have also checked prompts documentation but it look as if it weren't possible out of the box.
My bot is running on FaceBook, Perhaps it's not so important.
Currently, this is not a feature of the existing prompt system in BotBuilder SDK as of 5/8/17, but you are welcome to contribute this feature via a pull request to Microsoft/BotBuilder.
Please check out AdaptiveCards: http://adaptivecards.io/
Here is the GitHub repo: https://github.com/Microsoft/AdaptiveCards
Here is the npm package: https://www.npmjs.com/package/microsoft-adaptivecards
Adaptive Cards enable prompting users with images they can click on (just what you're looking for).
We have a Gmail Contextual Gadget, it is published in Google Apps Marketplace.
For OAuth1.0 to 2.0 migration, as recommended in https://developers.google.com/apps-marketplace/v1migratev2 we created a new version of our Gmail Contextual Gadget, published it in Google Apps Marketplace, and associated it with the old version.
Now, to the question: the old version of the gadget was installed in about 50 domains. What happens to them after September, 30? Do they migrate automatically? Or what do we need to do so that our users could continue using our gadget?
UPD:
As soitof pointed out, Step 4 of the migration guide suggests that we call 'PUT https://www.googleapis.com/appsmarket/v2/upgradableApp/listingID/cwsID/domain'
Yet, I am unsure about how to proceed from here. Namely, what the migration strategy should be.
The first thing is that we don't keep the list of domains where our gadget is installed,
we only have the number of domains. I suppose we could track the requests and build that list.
Here comes the second point: do we fire that PUT requests manually? It is not difficult for our 50 domains, but what if there were, say, 10000? My wild guess would be that we make the old version of our app fire that PUT request automatically, but I am not sure if that's a good idea.
I would welcome some advice, 'best practices', 'guidelines' etc. on how it is usually done.
No they will not migrate automatically, you have to migrate them. Its a simple task you just need a bit of info about your old and new app.
All the info is found here:
https://developers.google.com/apps-marketplace/v1migratev2
UPDATE:
So to migrate you will need two versions of your gadget published, one in the old market place and one in the new one.
So right now you have your old GamV1 gadget listed, you'll need to submit your new one for publishing. Once it is approved, and listed, you can begin the migration. You have to wait till it's published since you need information from its public listing.
You'll need to build a list of domains and perform the PUT on each one manually. I made a script that performed the PUT on a domain name, then made a wrapper script that fed it domains one by one.
I'm trying to develop a site, where users will be registered directly on it, as opposed to being authenticated by Google mail etc. Beside the usual username/password I need to collect more data from the user - name, address, etc. What would be the quickest way for adding the desired functionality? Short of writing my own Auth plugin I see two options:
Create my own registration form (which I kinda need to do anyway) and use HashDB for storing the passwords and later authentication. However, yesod.auth.hashdb seems to be gone from the latest version (why?) and is only available separately here: https://github.com/ollieh/yesod-auth-bcrypt/ . Is something wrong with it? Security flaws?
Use http://hackage.haskell.org/package/yesod-auth-account - looks much closer to what I need, because it already provides registration page, but it doesn't seem to be supported by the latest yesod 1.2.5 and it is not clear how to integrate my additional fields into the existing registration process
Does anyone know of a complete, downloadable/copyable example of a WiX installer that allows the user to select an existing website when installing a web application?
I'm trying to get this working and, after seeing that it seems to be a significant piece of work, I'd like to get an example running first so that I have a working project to base my own work on.
I found this (code is pasted as images) and this (can't get it running).
Just to confirm... Is it really as much work as the sites above suggest to allow a user to select the site to install to? Am I missing a trick?
I found this blog post that does the custom action in C# and has a complete downloadable sample. Pretty easy to follow.
Yes, that would be quite a bit of work to do it in WiX. I don't typically give a user this much choice. You might just want to do it as an after install configuration step if it's important to you.