- Invision Power Services
- → Viewing Profile: Topics: TSP
Community Stats
- Group +Clients
- Active Posts 822
- Profile Views 94,035
- Member Title Spam Happy
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Male
-
Location
Bergen, Norway
IPS Marketplace
-
Resources Contributor
Total file submissions: 4
User Tools
Latest Visitors
Topics I've Started
Why do I get logged out from these forums regularly?
17 May 2013 - 11:52 PM
Make it easier to give elements unique styles based on page type
23 April 2013 - 08:32 PM
Hi,
I had a case where in my template I wanted to have less padding on the maintitle-class in topics. The "issue" was that there was not any parent class that was unique for the page. So I would have to add my own class to the element that used maintitle on the page instead.
Which got me thinking, what if you added a class to the body-element to indicate what kind of content there was on the page?
Classes could be named something like
— topic-view
— forum-view
— index-view
— search-view
— profile-view
And it would look like this in the body-tag:
<body class='ipboard_body topic-view'>
And could then be used to create a new style rule that would override the default one.
.topic-view .maintitle {padding:3px 10px;}
I wouldn't expect IPS to use these classes themselves in their CSS, but it could help other designers achieve what they want in some cases.
For my problem however, I eventually realized that for the topic view the maintitle class was used on a div element, while on other pages it was used on a h3 element, so I ended up doing this:
div.maintitle {padding:3px 10px;}
Which didn't seem to "break" the style for the .maintitle class any other places.
Splitting quotes in WYSIWYG in 3.4.4. Not possible anymore?
13 April 2013 - 07:46 PM
I have a question, is it no longer possible to split quotes in the WYSIWYG now? This should be possible, like it was earlier in 3.4.X.
I have tried both normal enter twice in a fast matter, backspace then enter, shift enter, and other combinations of these I could think of, but I'm not able to split the quotes in WYSWYG. How is this supposed to work in 3.4.4?
I can imagine this was one of the things causing issues, but when you did add rendered quote boxes in 3.4.X it should be possible to split them in wysiwyg aswell. Splitting quotes is something our users are VERY used to doing in the editor on 3.2.X manually with copy / paste of the quote code.
If/when we upgrade I don't want to tell them to have to switch between RTE / STD to do such a basic action.
It also doesn't make for good user friendlyness when a bug patch release changes something like this... A patch upgrade from 3.4.3 to 3.4.4 should not change how the user has to do things / what he is used to is possible. I think you should actually atleast include this in the patch notes if you removed this.
I use Chrome.
Could you please update the GDK?
22 March 2013 - 07:12 AM
http://community.inv...-ipboard-32-33/
Could you update this? It doesn't seem to contain all the icons, I can't see
or
. I haven't looked very much into this, but could be other icons that are missing aswell?
(If they're in the GDK but I just can't see them, please tell)
Small update request on login modules documentation
25 February 2013 - 11:01 AM
I read this: http://www.invisionp...gin-modules-r42
The $password variable that is passed to this method has already been run through the IP.Board input cleansing routines, meaning certain characters have been replaced with HTML entities. If your external application does not do the same thing, this may mean passwords with special characters will fail if you do not account for this. The special characters that IP.Board will replace are:
You may wish to convert these characters back to their original form in the $password variable before sending it to your remote application for validation, if appropriate.
- \ to \ ; ( no space between 2 and ; )
- ! to !
- $ to $
- & to &
- " to "
- < to <
- > to >
- ' to '
And I fell into the trap of writing my str_replace in the order the chars were mentioned.
And this may be extremely obvious (I might be the stupid one here...), but it took me quite a while to figure it out. I'm thinking that other developers possibly could fall into the trap aswell.
Causing input pw! to be converted into pw&!
So I think it would be a good idea to
1. Move & to & at the top of the list
2. Add in a description that it's important it's the first replace done.
- Invision Power Services
- → Viewing Profile: Topics: TSP
- Privacy Policy
- Community Rules ·




Find content