Topic: FamilyForum Changelog:

[Ken (OP)]

Looking good so far on my XAMPP. 

Thrashing around a bit with no errors and searching for tags returns none found, also, the Tags icon is no longer in the TP Admin panel.

[Mick]

Looking good so far on my XAMPP. 

Thrashing around a bit with no errors and searching for tags returns none found, also, the Tags icon is no longer in the TP Admin panel.

Thanks Ken.  Hopefully it will behave.  I haven't checked the logs since yesterday, I'll do this after work.

I have this version installed here, http://www.tinyportal.net/index.php and on the test site here, http://cctestsite.info/testsite2/index.php So fingers crossed and all that. 

[Skhilled]

I found an error with the shoutbox but not sure how I did it.

http://www.docskillz.com/tp/index.php?action=forum

Notice the breaks. I did it the first time I made a shout but made a few others and can't reproduce it. It happened when I edited the 1st shout. Hmmmm....but no errors in the log.

Hope that was a glitch.  Has it done it since Steve?

Now guys, I realised that while it had the Topic and Post tags removed from that last zip, the Tags icon was still there and working in TP admin, and was still there at the bottom of articles when you create or edit them.  The latest zip which is attached below has all the tagging system removed.    Remember to un-install any previous version prior to installing this one. Please give it a good test for me. Cheers.

Sorry, been a bit tired lately. So far, can't get it to do it again. I'll try the newer version and see how it goes...

[Skhilled]

I added this in the shout:

Testing... 

But see this in the shout editor in the admin for it:

Testing... 

[Ken (OP)]

I added this in the shout:

Testing... 

But see this in the shout editor in the admin for it:

Testing... 

+1... doing the same for me.

EDIT: If you go through the edit process again it adds another "Â" each time.

[Skhilled]

Still not sure how it created the

Code: [Select]

<br />, tho...

[Mick]

I added this in the shout:

Testing... 

But see this in the shout editor in the admin for it:

Testing... 

Thanks, I actually noticed this yesterday after installing a fresh local testbed.  If you type your shout and don't add a space and just click the smiley it'll work ok, and add the space for you.  If you add a space after your shout, and then add a smiley you get the Â.  I'm sure. and Ken will probably remember, we had this same problem a while back when bloc was trying ideas for the shoutbox.  To be honest I thought that got fixed.  Will have to look through the repo and see what happened and when.

Thanks for the heads up on this.

Code: [Select]

<br />  issue though, that one I've not seen that one before

[Ken (OP)]

@Mick, saw you testing the Shoutbox here on OFF, this latest TP isn't installed here yet... but me gonna do it now. 

[Ken (OP)]

TP 1.111 installed here now.
The "Â" is still showing up with a edit of the Shouts.
Nothing in the error log, not even after I go into the Blogs and that's where some errors were generated in the past.

Post preview is still broken.

EDIT: Finally got it to throw an error for the Blogs. 

[Mick]

TP 1.111 installed here now.
The "Â" is still showing up with a edit of the Shouts.
Nothing in the error log, not even after I go into the Blogs and that's where some errors were generated in the past.

Post preview is still broken.

EDIT: Finally got it to throw an error for the Blogs. 

Yep, I haven't had a look into the  problem yet, but will do asap.  Though its a pretty minor thing tbh, t would be nice to fix it. 

As for the blogs Ken, I think you'll have to ask over at its support site for more ideas on this.

[Ken (OP)]

TP 1.111 installed here now.
The "Â" is still showing up with a edit of the Shouts.
Nothing in the error log, not even after I go into the Blogs and that's where some errors were generated in the past.

Post preview is still broken.

EDIT: Finally got it to throw an error for the Blogs. 

Yep, I haven't had a look into the  problem yet, but will do asap.  Though its a pretty minor thing tbh, t would be nice to fix it. 

As for the blogs Ken, I think you'll have to ask over at its support site for more ideas on this.

That's not going to happen. 
Feline stopped supporting her Blog a long time ago, actually, from what I see on her site it's difficult for users of her PortaMx portal to get any support.

At some point the blog will become so out of date and broken that it will have to be removed, but that time is still a little ways off.

[Mick]

TP 1.111 installed here now.
The "Â" is still showing up with a edit of the Shouts.
Nothing in the error log, not even after I go into the Blogs and that's where some errors were generated in the past.

Just got a heads up on this problem,

The the  appearing in the shout edit, seems to be a char set issue and UTF-8 seems to fix it.seems to fix it.

if you view the source if your page, do you see

Code: [Select]

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> somewhere in the header?

http://www.tinyportal.net is already converted to UTF-8 which is why the problem doesn't arise there.  Not sure if there's an easy fix for this, other than converting to UTF-8.  Hopefully bloc or Brad might have some ideas on this.

Actually (just a side note) I believe when you install SMF 2.1 it defaults to UTF-8, so perhaps this is the way to in the future.

[Ken (OP)]

I'll take a look at the UTF-8 setup and the SMF 2.1 as well to see if that's a possibility here on OFF. I've never really looked at the UTF-8, so don't know if it makes sense or not?

[Mick]

I'll take a look at the UTF-8 setup and the SMF 2.1 as well to see if that's a possibility here on OFF. I've never really looked at the UTF-8, so don't know if it makes sense or not?

Ken, the SMF 2.1 stuff was just a reference, TP isn't compatible with 2.1 and doesn't work properly.  Just saying that when people do eventually move to 2.1, they will automatically be on UTF-8.

I have no idea if converting this site to UTF-8 will break anything, it shouldn't but there's always a risk.

[Skhilled]

I haven't used UTF-8 in ages. The last time I did there were issues with it so I gave up on in and went on to other things.

So, I'll switch the test site over and see what happens. Personally, I was leaning toward a language or UTF-8 issue myself as the reason for it.