I Have 2 different dashboards and I am trying to link both the dashboards through links such that both the dashboards are accessible throught one other. I cannot put both in same page as load time will be more. The approach i have taken is by using drilldown
<drilldown>
<link target=_blank> link to another dashboard </link>
</dashboard>
But this doesnot work for me :/
If you want to drilldown into another dashboard, it will look like this
<drilldown target="My New Window">
<link>
/app/dashboard_examples/form_table2
form.sourcetype=$row.sourcetype$
</link>
http://docs.splunk.com/Documentation/Splunk/6.0.2/Viz/Dynamicdrilldownindashboardsandforms
Related
If the event has a URL and you want to show the URL in a search table where you can make the URL a clickable link that will go to that URL how do you do this?
for now, I'm doing this:
<drilldown>
<link target="_blank">$row.URL|n$</link>
</drilldown>
and it's working , but that's make all of my row to lead into this link, and i want that only when you click on the specific URL it will lead you to this link
To allow the user to click on a URL and be taken to that link, use $click.value2|n$ as the drilldown target.
<drilldown>
<link target="_blank">$click.value2|n$</link>
</drilldown>
There's an example in the Splunk Dashboard Examples app (https://splunkbase.splunk.com/app/1603)
I have many many pages on my website. Among those numerous pages I have a lot a html tables with the class name : class="scrollable"
I'd like to add the class="nolazy" to all the images contained by all the <table class="scrollable"...> throughout my website.
It would be painful and long doing that by hand page after page. I don't even know how I could easily spot list the pages which have a with images inside.
I made my website with a custom template in wordpress
Can I do this with a plugin (would be the best) ?
Can I do this with a sql query ?
Thanks for your help,
François
I'll post this as an answer if that's what you are looking for.
Wordpress plugin guide:
https://developer.wordpress.org/plugins/
https://www.wpbeaverbuilder.com/creating-wordpress-plugin-easier-think/
Querying wordpress page:
https://developer.wordpress.org/reference/functions/get_pages/
HTML DOM Parser:
https://github.com/Rct567/DomQuery
Mix it all together and you will for sure achieve the result :D
I say I have a section of a page like this (rough HTML to give an idea):
www.mydomain.com/contact-us
<div class="regional-offices">
<div class="south-west">
South West
<div class="south-west-content">South west office address</div>
</div>
<div class="north-east">
North East
<div class="north-east-content">North east office address</div>
</div>
...
...
Currently, these are a set of accordions that expand to show the content when the link is clicked. What I would like to do is treat them as individual URLs so that they can be seperately indexed by Google, as of course at the moment they are just part of a single page.
I have been researching the History API and can see how I would do this as far as creating unique URLs for each section, but where my understanding falls down is how Google or other search engines will handle these links if the required info is already part of the page and not stored at its own seperate URL.
For instance, the first step would be to change the <a> tag to be something like:
North East
We can then use JS to preventDefault() going directly to the URL, and instead provide the user with an expanded accordion, bring the page scroll down to the accordion and a unique URL using the History API. This is all well and good if we visit the URL directly, or click any of the links.
But the problem is that as far as I know, the Google crawler will try to follow the link and be faced with a 404 because there's no Javascript preventing access to the resource in the URL. And nor do I want there to be.
Or is it the case that I will need a unique location holding the contents of the accordion, which is indexable, and also pulled in with AJAX when a collapsed accordion is interacted with?
Apologies if I haven't made anything clear.
I had to deal with the same thing. What I did was to make a rewrite rule so that the link that google follow is actually posted to the page that handle the the request. to display the data. Angular might save you a lot of trouble to dealing with accordions.
I have a page that consist of a daily updated front page with every day archived in a sub-page. The sub pages are either a funny picture or a joke. The pictures and jokes have a like and share option (for facebook, stumbleupon and pinit for instance), which obviously link to the picture or joke in question. I'm puzzled what to do with the google plus button though.
What is good pratice? Link to google plus with the link straight to the picture (sub-page) or set it up to share the main page?
so this:
<div class="g-plusone" data-size="medium" //...// data-href="http://www.amazingjokes.com/"></div>
or this:
<div class="g-plusone" data-size="medium" //...// data-href="http://www.amazingjokes.com/?view=img&date=2013-06-16"></div>
Thanks
I would concur with what Scarygami says, but also add that this may be a scenario where an interactive post/share might be appropriate as well. You could have the shared info go to your top level page, and a "Visit" button go to the more specific sub-page.
Really depends on what you want to do.
Linking the +1-Button to your main page will have an accumulated count for your page, while linking it to the picture will have a count per-picture which I think would make more sense in your scenario.
Of course you can have an additional +1-Button for your main page so people can show their appreciation for your page in general. If you have a Google+ Page associated with your site you could also use a page badge for this.
I have listing pages that take a page argument on the url like the following:
http://www.domain.com/foo/bar/?page=7
Should I just include the URL without params or should I list all pages in my sitemap.xml?
EDIT
Paginated content are listings, like an index. Therefore their content is also (in more detail) found in detail pages. But these paginated ones are the only way to reach detail pages.
I really wanted to find you a reliable source for this one, but I couldn't. Which means you'll have to make do with my intuition:
If the articles exist only in their paginated form, and you want them to be indexed as separate pages, list them all. They'll all have distinct content on them, so you won't be penalised for duplication.
I found details of one exception; including page 1 twice. Basically you need to choose whether the first page will be /foo/bar/?page=1 or just /foo/bar/, then do a 301 redirect from the version you don't want to use.
Hope this helps (even just a little).
Tom
NO!: You should add Meta-Tags to you paginated sites. This helps google to understand your pagination system.
Example:
On page 1 you would add into <head>:
<link rel="next" href="http://www.example.com/article?story=abc&page=2" />
On page 2 you would add:
<link rel="prev" href="http://www.example.com/article?story=abc&page=1" />
<link rel="next" href="http://www.example.com/article?story=abc&page=3" />
On page 3 you would add:
<link rel="prev" href="http://www.example.com/article?story=abc&page=2" />
<link rel="next" href="http://www.example.com/article?story=abc&page=4" />
And on page 4 you would add:
<link rel="prev" href="http://www.example.com/article?story=abc&page=3" />
See this document: Pagination with rel=“next” and rel=“prev”
In this case the ?page=7 probably relates to the content management systems page. In you site map file you can add this. In the site map if you want each of these pages to be displayed in what ever uses this file yes you should add them.