Just found this and it's great! How simple yet perfect
And the autoplay feature is amazing
"Last Changes" - Double Panel
By gwpl
Description
This panel let you check both :
- last page changes
- last forum post
At one time !
Code
[[div style="float:left; border: gray 1px solid; width: 56%"]]
Last changes on : **forum**
[[module RecentPosts]]
[[/div]]
[[div style="float:left; border: gray 1px solid; width: 41%"]]
Last changes on : **Pages**
[[module SiteChanges]]
[[/div]]
In action
Ostatnie zmiany na : forum
Why isn't there a nice red button that says "Open New Tab"?
in discussion Hidden / Per page discussions » URL Title with Slash Redirect
Great!
I think it's still a Wikidot bug though; there's no good reason why % should be invalid in titles.
Hmm, not sure if it's something that Wikidot can do. The error is likely being thrown somewhere lower in the stack (i.e. not in Wikidot's codebase).
Most web servers will trip over trying to parse a URI with % but not followed by two hex characters. What happens when that occurs isn't defined. But when it happens after the hash, you're at the discretion of the browser's implementation.
See recommendations on w3.org:
Sequences which start with a percent sign but are not followed by two hexadecimal characters are reserved for future extension.
The ideal solution is for Wikidot to provide a way of variables with percent encoding — e.g. %%title|urlencode%%.
Kenneth Tsang (@jxeeno)
in discussion Hidden / Per page discussions » URL Title with Slash Redirect
That's got it. Thanks.
I think it's still a Wikidot bug though; there's no good reason why % should be invalid in titles.
in discussion Hidden / Per page discussions » URL Title with Slash Redirect
Ah, dang. Didn't test that.
I've just updated it to use escape(unescape()) — let me know if it's working better. Based on that link on feedback.wikidot.com, looks like it's working now.
escape(unescape()): the first unescape will ensure any encoded entities are correctly decoded first, and then encode all special characters except / unless it's after the /title/. I think this solves it.
There's still an edge case where the user might provide a page title with a substring that is in the URI encoding format. For example, if the title was to be: Problem with encoding %20. I don't think it's possible to fix that though.
Kenneth Tsang (@jxeeno)
in discussion Hidden / Per page discussions » URL Title with Slash Redirect
Sorry, that's worse.
The problem is that there are already bona-fide % characters in the URL replacing space characters in the page title:
…/title/Re:%20Expect%20a%2015%%20performance%20loss%20coming%20soon
The fix to escape the % in "15%" also escapes all the others, with the result that the new page title has all the escapes in.
The only way I can think to fix this is to go back to the original and make a special case of a "%" that is not followed by a hexadecimal digit:
var urlfix=unescape(window.location.hash.substring(1));
urlfix = urlfix.replace(/%[^0-9A-Fa-f]/g, function myfunction(x) {return "%25"+x.slice(1);})
(Warning: I have made it a career ambition never to learn Javascript.)
That will lead to odd behaviour when the % is followed by a digit, but I can't see an obvious solution.
On reflection, I think this is a Wikidot problem. I've filed a bug report there: http://feedback.wikidot.com/bug:1152
in discussion Hidden / Per page discussions » URL Title with Slash Redirect
Wow. That was some pretty terrible code 😂
Gone back and made some changes. The modified version shouldn't break any existing code (unless the use case is to generate broken URL encoding).
If anyone else is experiencing new problems as a result of this change, please reply below with an example :)
Kenneth Tsang (@jxeeno)
in discussion Hidden / Per page discussions » URL Title with Slash Redirect
I have used this to create comment pages in a forum build:
[[span class="forum-button"]][[[http://snippets.wdfiles.com/local--code/code:url-title-with-slash-redirect/1#http://srhdev.wikidot.com/comment:new_comment/edit/true/parentPage/%%fullname%%/title/Re:%20%%title%% | Reply]]][[/span]]
It has worked fine for years, until someone just created a thread called "Expect a 15% performance loss coming soon". On that page, the button produces a 400 error. The URL it produces is:
http://snippets.wdfiles.com/local--code/code:url-title-with-slash-redirect/1#http://srhdev.wikidot.com/comment:new_comment/edit/true/parentPage/thread:834/title/Re:%20Expect%20a%2015%%20performance%20loss%20coming%20soon
The "%" not quoted, which it should be.
| header | header | header |
|---|---|---|
| 67 | иван | дф 78 |
| cell-content | cell-content | cell-content |
in discussion Hidden / Per page discussions » Todo List with Data Forms
[[include :snippets:todo:_list]]
I have only the special style settings on http://snippets.wikidot.com/code:collapsible-block-unleashed
The "collapsible" line itself I have seen somewhere, but I think this is not so easy to sovle
Perhaps the old guide from div style settings does help you?
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
Is there any way to change the color of the collapsible?
So I took a look at http://try.wikidot.com/color-tab-testing
Not blue, finally green! Except for this part. Why can't I change this, too?
use this code to change the field color:
.yui-navset .yui-content {
background: #434b98;
}
#434b98 is dark blue. You can use this site to pick the color you want, it's simple to use.
Where can I change THIS text color?
.yui-navset .yui-nav .selected a, .yui-navset .yui-nav .selected a:focus, .yui-navset .yui-nav .selected a:hover {
color: #dd00ca;
}
#dd00ca is magenta. Replace it with the color you want to use.
I suggest you use the developer tools for this. Each browser (non-mobile) should have these, you can look at the styles with them and play around without actually messing up the design. I use a Chromium-based browser, and activate the developer tools through Ctrl+Shift+I, which opens a new window for me, with the page's html on the left side, and its css on the right side. Here's a screenshot.
Nor can I link to the specific test page I've been using.
- the reason is the "newbee" factor for you! Your karma is low and you are new on Wikidot: the spam-filter is stopping you from posting a link at the beginning of your life here in the wikidot platform:
we have an unbelieveble wave of spammers on many wikis - for better search results (SEO-technic) , last year were >80.000 free wikis deleted because of spamming with external links to their business site ( and the owner too).
I am not sure how to change all of the fields in the tabs
I have copied your test page http://try.wikidot.com/color-tab-testing ( I can post with my karma here) to a new one http://try.wikidot.com/color-tab-testing-1 without the module CSS at the top - for playing around with the color-codes.
let us comment on these pages the colors..
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
A somewhat new problem has arisen; I am not sure how to change all of the fields in the tabs. Nor can I link to the specific test page I've been using.
In trying to create an example to show you where I am having issues with the code, I discovered my problem: the color change code will not show up until you save it; I had been exclusively using 'preview' until now.
All is well (ish)
Which community do you mean?
http://community.wikidot.com/ is our community and on the forum you need not to be a member to post something…
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
It helps a bit; I only need to change it on the one page. The problem is that I can't seem to get any of the hex code to take? I've requested to join the community to post the code I have.
You can use this CSS code on the top of any page - working for this page only ! - or on the Custom Theme ( see your site manager) for ALL pages of your wiki.
This is the code for the page alone CSS coding: ( see also documentation on http://www.wikidot.com/doc-modules:css-module )
[[module CSS]]
/* TABS */
.yui-navset .yui-nav a,
.yui-navset .yui-navset-top .yui-nav a {
background-color:#d8d8d8;
background-image: url(http://lastlook.pl/~quake/wikidot/images/yuitabs.png);
}
.yui-navset .yui-nav a em,
.yui-navset .yui-navset-top .yui-nav a em {
border-color: #a3a3a3;
}
.yui-navset .yui-nav .selected a,
.yui-navset .yui-nav .selected a:focus, /* no focus effect for selected */
.yui-navset .yui-nav .selected a:hover { /* no hover effect for selected */
background:#700 url(http://lastlook.pl/~quake/wikidot/images/yuitabs.png) repeat-x left -1400px; /* selected tab background */
color:#fff;
}
.yui-navset .yui-nav a:hover,
.yui-navset .yui-nav a:focus {
background:#d88 url(http://lastlook.pl/~quake/wikidot/images/yuitabs.png) repeat-x left -1300px;
}
.yui-navset .yui-nav,
.yui-navset .yui-navset-top .yui-nav {
border-color: #444;
}
[[/module]]
You can find lots of help on the community howtos: *community.wikidot.com/howto:_start
Hope this helps?
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
I keep seeing this, but I do not quite understand what that means. Or how to do it. A step by step would be lovely, and/or code to just throw on individual pages would also be keen.
Ostatnie zmiany na : stronie
| chatbox: s | N | 09 Sep 2018 02:12 | (new) | shiro123456 |
| chatbox: it does works | N | 28 Aug 2018 16:29 | (new) | SEC_the acronym |
| chatbox: hi | N | 28 Aug 2018 16:28 | (new) | SEC_the acronym |
| chatbox: it works | N | 17 Jul 2018 11:01 | (new) | Slaylebrity |
| todo: Test Page | N | 20 Jun 2018 05:34 | (new) | Tristyn |
| chatbox: some1 help me ples | N | 13 Mar 2018 20:55 | (new) | ProGamerAL |
| chatbox: now icant edit my page again | N | 13 Mar 2018 20:54 | (new) | ProGamerAL |
| chatbox: well | N | 13 Mar 2018 20:54 | (new) | ProGamerAL |
| chatbox: hello | N | 03 Mar 2018 18:47 | (new) | NGExecutive |
| chatbox: hi | N | 05 Feb 2018 22:11 | (new) | nsturtz2 |
| code: URL Title with Slash Redirect | S | 04 Jan 2018 11:32 | (rev. 10) | tsangk |
| code: URL Title with Slash Redirect | S | 04 Jan 2018 11:28 | (rev. 9) | tsangk |
| code: URL Title with Slash Redirect | S | 04 Jan 2018 11:27 | (rev. 8) | tsangk |
| code: URL Title with Slash Redirect | S | 04 Jan 2018 11:25 | (rev. 7) | tsangk |
| code: URL Title with Slash Redirect | S | 04 Jan 2018 02:07 | (rev. 6) | tsangk |
| code: URL Title with Slash Redirect | S | 04 Jan 2018 01:58 | (rev. 5) | tsangk |
| todo: New-Item | N | 26 Dec 2017 16:55 | (new) | stas_proskudin |
| chatbox: How do I do this? | N | 18 Dec 2017 19:54 | (new) | Cygnar4Life |
| chatbox: What’s up? | N | 30 Nov 2017 10:53 | (new) | k-cal |
| chatbox: Hi | N | 25 Sep 2017 22:22 | (new) | Graic |
Thanks to tsangk for this great snippet: conditional-blocks
text above inserted with:
[[include :snippets:if START |unique=1|type=equal|var1=%%name%%|var2=conditional-blocks]]
**##red|Thanks to tsangk for this great snippet:##** [[[code:conditional-blocks]]]
[[include :snippets:if END]]
Other snippets posted by gwpl
Rate this solution
If you think this solution is useful — rate it up!
Add a New Comment
page revision: 7, last edited: 16 Feb 2012 01:17
