I have an Eloqua microsite that I would like to integrate into my main website as smoothly as possible. The site is a single page, and I am am hoping to include it as a subdirectory rather than a subdomain e.g. www.mydomain/microsite.
Is it possible to do this with an Eloqua microsite.
currently Eloqua only works with subdomains, not subfolders.
Related
we are trying to deploy a web page on a gcp project. The site is working but the we would like to change the auto generated url to something more user friendly.
The auto generated URL goes something like: dev-dot-project-numbers.uc.r.appspot.com/
Is there a way to customize or change that url?
thanks
Yes, you can. That URL looks like one for App Engine, which you can make available at your own address. You need to control your own domain (there are lots of services where you can get one). Then follow the instructions at https://cloud.google.com/appengine/docs/standard/python3/mapping-custom-domains to have your App Engine app respond at an address in your own domain.
I am creating a rails website which needs the ability to create subdomains, however, the admin panel which can create these subdomains needs to also be located on its own subdomain so that the parent domain is separate.
Is it possible to create subdomains from a website already on a subdomain?
Sorry if it's hard to understand, I struggled to explain it.
Thanks.
Actually you can have just one application responding to how many domains you want. Just need to user proxy_pass if you are using nginx
Check this: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass
I'm a website designer who's fairly new to rails. I'm building a custom CMS for the websites I design.
The idea is that clients will be able to login to their cms panel (on their individual domain and hosting) and can submit a support ticket which will be forwarded to my admin panel on my domain and hosting.
Is anyone aware of a learning resource for this type of function?
Any advice would be great, thanks.
Rails is primarily built to handle web requests, so that's the most straightforward way to interact between Rails apps. Just create a post request containing the ticket info, targeted at your admin panel app, which has the typical Rails setup to handle it.
Rails uses helpers called routes to efficiently handle form submissions. Instead of the expected route any form_for #mymodel can specify a url to send the form to, ostensibly to an offsite url as you desire.
I am pretty new to RoR development and newer to LocomotiveCMS...that said, I am trying to build a relatively simple site with LocomotiveCMS. Ideally, I would like to restrict the entire site from anonymous users, and then extend the roles as read-only, contribute, admin, etc. I see that Locomotive uses devise for authentication for /admin. Is there a way to restrict access to only authenticated users?
The easiest way to do this would be to make every page unpublished. Users would then have to be logged into the CMS to be able to see any of the pages.
This PR adds switch in page settings for restriction of anonymous users.
I'm running a site which allows users to create subdomains. I'd like to submit these user subdomains to search engines via sitemaps. However, according to the sitemaps protocol (and Google Webmaster Tools), a single sitemap can include URLs from a single host only.
What is the best approach?
At the moment I've the following structure:
Sitemap index located at example.com/sitemap-index.xml that lists sitemaps for each subdomain (but located at the same host).
Each subdomain has its own sitemap located at example.com/sitemap-subdomain.xml (this way the sitemap index includes URLs from a single host only).
A sitemap for a subdomain contains URLs from the subdomain only, i.e., subdomain.example.com/*
Each subdomain has subdomain.example.com/robots.txt file:
--
User-agent: *
Allow: /
Sitemap: http://example.com/sitemap-subdomain.xml
--
I think this approach complies to the sitemaps protocol, however, Google Webmaster Tools give errors for subdomain sitemaps: "URL not allowed. This url is not allowed for a Sitemap at this location."
I've also checked how other sites do it. Eventbrite, for instance, produces sitemaps that contain URLs from multiple subdomains (e.g., see http://www.eventbrite.com/events01.xml.gz). This, however, does not comply with the sitemaps protocol.
What approach do you recommend for sitemaps?
I recently struggled through this and finally got it working. See this thread for more details:
http://www.google.com/support/forum/p/Webmasters/thread?tid=53c3e4b3ab8d9503&hl=en&fid=53c3e4b3ab8d9503000497bd04ba63cf
Summary:
Use DNS verification to verify your site and all it's subdomains in one fell swoop
make the robots.txt on all your subdomains point to the main sitemap on your www domain
You may need to wait several days for Google to update it's cached copies of robot.txt on all your subdomains. It will still show errors until then.
Yes, the subdomain restriction is in the sitemaps.org spec, but, Google has put some exceptions in place:
Verify all subdomains within your Google Webmaster tools account
http://www.google.com/support/webmasters/bin/answer.py?answer=75712
cross-submission of sitemaps XML via Google Webmaster tools - if submitted via the root of your domain - will not throw errors for Google
Within the robots.txt of a subdomain you can point to sitemaps XML on other domains. there will be no cross submission errors - for Google
If you have a website that allows users to create sub-domain within your site, it is better for you to simplify the process by creating and submitting sitemaps for each subdomains by creating a single sitemap. This includes sitemap URLs for all your subdomain sites and saving this sitemap to a single location. But, to do this, all sites must be verified in webmaster tools. You can define one sitemap as:
http://example.com/sitemap.xml
Define all your sub-domain sitemaps for all your sub-domain URLs under this document tree.
You can define multiple sitemap files upto 50,000 URLs and 10 megabytes file size per sitemap. Sitemaps can be compressed using gzip to reduce the bandwidth. So, you don’t have any problem by defining the sitemap in this way.