Find content
Male
It's a standard CSS 2 selector, it's supported by IE7+ and all other browsers.
- TSP likes this
#2396698 Make it easier to give elements unique styles based on page type
Posted by
on 24 April 2013 - 04:12 AM
#2396696 Make it easier to give elements unique styles based on page type
Posted by
on 24 April 2013 - 04:06 AM
Interesting. Might be able to use something like <body data-location="app_module_section">
This way you can use:
body[data-location^=forums_topics] h1 { padding.... }
- Ryan H., teraßyte, Marcher Technologies and 2 others like this
#2394772 Fastest support ever?
Posted by
on 18 April 2013 - 03:04 AM
It sounds impressive, but Rhett has a time machine app on his giant phone. It actually took him a week to make the fix.
- Wolfie, Ryan H., Adriano Faria and 9 others like this
#2387121 Social share has a huge gaping hole - pm this link
Posted by
on 27 March 2013 - 07:49 AM
okay Matt, you made your point but I would think that if you stood in Piccadilly Circus and asked passers by, one by one, what the symbol meant, most of them would not know.
Aunt Madge would certainly not know until I told her and I really don't want to have to spend any more time with her than needed.
My point is that tech savvy folks know but the average user does not know that Share =
matts_secret.jpg
I phoned your Aunt, and she said she knew exactly what it meant. I also stood in Piccadilly circus and asked passers by. Not many stopped to give me an answer, but I did collect £1.78 in loose change tossed at my feet, so not a complete waste of time.
- stoo2000, Myr, The Old Man and 10 others like this
#2387061 IPB, BBCode, and concerns about it's future
Posted by
on 27 March 2013 - 05:15 AM
Just to offer a return comment...
Using the clipboards to paste the information I wanted did not work.
The editor does not properly format information that has vertical columns.
Worse, when you post something and then go back to edit it, all kinds of HTML crap is introduced into the mix.
This really is a bad editor and I hope IPS is serious about upgrading it.
What you need to do is ask the administrator to enable HTML posting for your member group but you must only enable this for trusted member groups as allowing full HTML posting to be made allows you to post javascript and other items that can be used to leverage an XSS attack. But for admins and moderators, there's no reason you can't have this enabled.
The issue isn't that the editor is broken or adds "all kinds of HTML crap", it's just that it is doing exactly what is asked. It's taking your raw content and stripping out undesirable elements and formatting that can be used to break the board's display and items that we don't have BBCode for (such as tables).
I understand that it doesn't give you the result you want, but it's an important distinction to make.
It's actually very difficult to get the balance right with allowing rich mark-up but denying items that can be used to break the board. For example, it's highly likely that a lot of content that you copy and paste is styled by external CSS which won't be copied across in the text's meta-data. Also, you may find some content has inline styles such as background colour which we strip. We also have to strip "class" attributes to prevent people from copying and pasting IP.Board CSS classes that may disfigure the topic.
If you do see "HTML crap" when you go to edit the post, then that would be a bug and I'd urge you to post a bug report. However, if you DO have HTML posting on and you are seeing the raw HTML code, this is because when HTML mode is used, we disable CKEditor so you have to edit the HTML by hand. The reason we do this is that a substantial number of customers use HTML posting to add in complex ad tracking javascript or complex affiliate links which CKEditor in an attempt to make the content safe strips.
- ΑndyF, Marcher Technologies, Atsuki and 2 others like this
#2386639 IPB, BBCode, and concerns about it's future
Posted by
on 26 March 2013 - 06:41 AM
The CKEditor component is actually fine in terms of stability. If you read through the posts here, the majority of complaints are to do with the BBCode conversion, which we agree hasn't been as smooth as we'd hoped. It's actually incredibly complex because BBCode itself can be very complex and doesn't always tally up nicely with HTML tags.
As Brandon has said, we are working to make sure this part of the editor is improved for 3.4.4 along with the code and quote box issues.
I'm not suggesting that we are or should, but if we removed BBCode completely, 95% of the complaints and bug reports would vanish as CKEditor would be doing what it does best - cleaning and formatting rich text as HTML.
#2385042 3.4 Editor BUGGY.
Posted by
on 22 March 2013 - 07:26 AM
#2384058 IPB, BBCode, and concerns about it's future
Posted by
on 19 March 2013 - 08:50 AM
Thanks for taking the time to post that, it's definitely given me a lot to think about.
However, our plans are not to remove BBCode in 4, but merely shift all processing to one area.
We continue to fix the BBCode issues that are reported to us. Please take a moment to write up any bugs you come across and we'll make sure they're taken care of.
- ΑndyF likes this
#2382622 Messenger - Last reply
Posted by
on 15 March 2013 - 04:31 AM
#2382620 4.0: Adopt a naming convention for database columns
Posted by
on 15 March 2013 - 04:23 AM
As Mark says, it's often a challenge refactoring existing code. We always have to balance the impact of changes against our customers and as much as we'd like to toss out the schematic and start again it's not really practical.
We do plan to make some broad changes to table naming which will help bring order to the database.
- Feld0 likes this
#2382604 Will there be IP Board 3.5?
Posted by
on 15 March 2013 - 03:05 AM
Our current plans do not include an IP.Board 3.5, we intend to maintain the 3.4 branch as needed until the release of 4.0.
Of course, if we feel the need for a 3.5 then we'll adjust our plans accordingly. In terms of timescales, it's always difficult to predict accurately so early in the product's development cycle. We recommend that you keep an eye on our development blog for more insight into the development process.
#2379877 How is the IPS Suite Going to Stack Up to Future Open-Source Software?
Posted by
on 08 March 2013 - 06:47 AM
Welcome!
I think you've already answered your own question:
I can honestly say that the IPS Suite provides the best solution for communities possible. It takes all the bloat off and puts all the content front-and center and isn't full of useless options and ugly chrome
We focus on community software, not just forums and provide you with the tools to build, manage and grow your community. From galleries to a fully featured commerce application.
All of which is backed by our technical support team who are there to assist you in getting the best from your software. We also offer a spam monitoring solution and a visual skin editing solution at no extra cost.
And on top of that I firmly believe that we have the best software which is actively developed by a very focused development team all of whom interact daily on the forums and in our blogs. We offer rapid turn around of product updates and we're always here if you want to talk to us about any ideas for future versions you may have.
Having a good "forum" isn't enough. You need a great forum that is part of a great suite of products that is backed by a great support team with bags of experience.
I think IPS ticks those boxes comfortably.
#2378116 I do not like 3.4
Posted by
on 04 March 2013 - 08:51 AM
Hi Joey,
I'm sorry that you've had a poor experience recently and that highly visible bugs have crept into the latest release. Perhaps you could consider setting up a staging site where you can test the beta releases we make? That way the issues you'd have spotted could have been reported to us before a final release has been made.
We do try to ensure all releases get sufficient testing internally but it's hard to replicate all the different configurations our customers use. This is why we make beta releases. This gives you a chance to test the new version on a staging site to identify these kinds of issues.
Indeed, I recommend that everyone does this. The more issues we get reported during the beta stages the better!
