I'm trying to get the customer's feedback on the quote instead of declining and entering reason.
Once the customer declined I have to create a new quote and send it again instead of correcting it.
Any ideas?
Is this embedded or remote? I'm guessing embedded if it's a quote.
One option is to use the "Finish Later" button. Then set a specific url route back to your app (Features -> Branding -> edit -> Landing Pages) such that that landing page within your app says something like "We see you had an issue with signing your quote. Please tell us how we can help" and provide the choices there. Continue processing based on their choice.
Though I'll say I don't think there's anything wrong with declining and re-creating after they correct the input. May be cleaner and easier that way.
Related
I'm a complete COMPLETE noob at Drupal.
I've been handed a large very customized Drupal 7 site after our admin quit. I have tons of WP experience, but zilch in Drupal.
I've been asked to edit a page that exists at:
http://my.drupalsite.com/[page]
The page functions only to redirect to:
http://my.othersite.com/
But, I need to change part of the way it redirects. Normally (as in, the one other time I did it) to edit a Drupal page, I just go to the page logged in as an admin and click "edit". Since this is a redirect page, I can't really do this. The /admin/content section has 83 pages of 25 items each with no way for me to search on anything and no way to tell from what the guy called the page as to what page actually does this redirect. I'll be a monkey's uncle if I'm going to click on every darn one of them and then click the "URL path settings" tab at the bottom to see which one of these suckers is the page I'm after.
Surely this is simple for even a typical Drupal novice... like I said though, complete noob.
Any ideas? Thanks!
There are a few modules that can handle redirection or even simple editing of a path.
You can look at pathauto
https://drupal.org/project/pathauto
On that page you should find other recommendations such as the Global Redirect & Redirect modules. I'm pretty sure some of these modules will simplify your task. You should be able to take an existing path and redirect it to wherever you wish, without having to dig in each URL alias on the node edit page.
It's always difficult to give specific advice without knowing more, but , for instance, Pathauto can help you change the path of a specific content type to a specific pattern. That can come very handy if you need to change a bunch of pages with a similar structure.
Is there a decent way in DNN 7 to modify the navigation block at the top? I am completely lost.
I am using the "Awesome Cycles" content as a template for a class project. All I am trying to do is change out the word "us" in the navigation at the top for the word "me".
I'm sure there must be an easy way to do it, but I don't think I "speak the language" well enough to google this. I have been literally searching for three days, and I know I'm going to feel stupid once someone points it out but... Oh well.
Thanks in advance!
You are correct that you can simple change the Page Name in the page settings to control what displays in the Navigation. But be aware that changing a page name also changes the URL of that page.
Check out this video for how to avoid bad URLs after changing pages
http://www.dotnetnuke.com/Resources/Video-Library/Viewer/Video/213/View/Details/Renaming-a-Page-in-DotNetNuke.aspx
tl;dr - create a new page, with the old name, make it hidden (not in the menu), and have it redirect to the new page.
I'm playing with Salesforce's "Sites" functionality today for the first time, whereby I can expose Salesforce functionality to anonymous users via VisualForce. It's cool, but I'm seeing some weird timing behavior. I've been trying to figure it out, but it's a mystery, so I'll ask here?
When I save my changes to my VisualForce page, I would expect to see the changes right away. Or at least, when I do a "real" save (by hitting "Save"), versus a "Quick Save," which I assume is what happens when I'm using the developer toolbar to edit -- or actually hitting the "Quick Save" button in the main VisualForce section.
At any rate, I save it as much as I possibly can, and I'm able to see the right thing when I go to the VisualForce page itself (not using the force.com URL). But when I go to the force.com URL, I'm seeing an old version of a page. If it's just a matter of waiting long enough, that's one thing. But it's acting like I'm doing something wrong.
During development, it is very helpful to add a cache="false" parameter to the apex:page tag. This should solve the issue.
Reference page for apex:page has other optional parameters as well.
I see some ads on my drupal website. No idea where they came from but I want to get rid of them. Any help appreciated
This one comes up from the bottom of the screen from time to time.
You can minimize it but it doesnt go away unless I close my webpage, and open again
It was related to Softonic Toolbar not something with Drupal.
I removed all the toolbars or that kind of unwanted programs which I installed(without conscience) then cleaned with Malwarebytes and CCleaner.
Now everythings fine
I had the same problem. I solved the problem by deactivating the ad option. To do this, simply click on the "ad option" at the bottom of the ad. You will get a page that mentions different things about the ad. Click on "deactivate" link. It will take to another page where you can deactivate the advertisement. It won't come back.
The problem I am having is filtering out the users that come to our homepage just to login, since we have the client button on the homepage (and yes I've tried to get them to put it somewhere else).
I can't think of a way to do it because they don't look any different than potential clients, other than that they may visit more often and click on the button. Any ideas or software that might accomplish this?
one way, is to associate a cookie with those users and either a) don't load the tracking code when cookie is present, or b) in Analytics Settings -> Filter Manager, add an exclusion pattern matching the cookie name. a) would be more flexible.
now, there's no way to tell if the user is going to stay on the main site or hop to the client area... so it might undercount in some cases. but you might find that better than the overcount showing up now...
a slightly more intrusive option, would be a JavaScript overlay / splash screen that shows up when you detect a user returning that asks them, "Would you like to go directly to your client area? [YES] [NO, TAKE ME TO THE MAIN SITE]". in that case, the tracking code wouldn't be loaded unless, they say are going to the main site...
if using the filter manager method, you'll want to register the variable like so:
<body onLoad=”javascript:pageTracker._setVar('my_cookie_name_guid')”>