April 10, 2007

Comment Problem

Hi everyone.

We seem to have a problem with comments not saving at times.  I've managed to reproduce the bug, but haven't tracked it down yet.

I'll keep you posted.

Update: The comment problem is fixed!  Hooray!

Posted by: Pixy Misa at 05:53 PM | Comments (39) | Add Comment
Post contains 40 words, total size 1 kb.

1 And... action!

Posted by: Pixy Misa at April 10, 2007 07:09 PM (PiXy!)

2 Bingo!

Posted by: Pixy Misa at April 10, 2007 07:09 PM (PiXy!)

3 I copied a post originally written in MSWord.  Now there are little smileys at the beginning and end of most lines??????????

Also, how can I set a category?

Help.

Posted by: erp at April 16, 2007 03:13 PM (9oHan)

4
I copied a post originally written in MSWord.  Now there are little smileys at the beginning and end of most lines?
Couple of ways to fix this:

One, turn off smilies for that post.
Two, select a new smilies set from smilies.mu.nu.  Those sets don't have same problem as the default set... I guess I should fix the default set.

Posted by: Pixy Misa at April 16, 2007 03:23 PM (PiXy!)

5 You are completely amazing.  Responding so quickly.   Time on comments is off by an hour (I know about the DST time issue), but the times for post is incorrent.

Will try changing smilies.

Is is not a good idea to copy and paste from an MSWord file?


Posted by: erp at April 16, 2007 05:31 PM (9oHan)

6
You are completely amazing.  Responding so quickly.
I'm really just a clever Javascript routine.
Time on comments is off by an hour (I know about the DST time issue), but the times for post is incorrent.
Okay, I'll look into that. They should work exactly the same, so there must be a problem there.
Is is not a good idea to copy and paste from an MSWord file?
Word has some funny ideas about formatting that can cause problems. There's actually a past-from-Word function in the editor which apparently works fairly well.  It's the little clipboard with the W on it.  Copy from Word, then click on that to paste.

Posted by: Pixy Misa at April 16, 2007 05:55 PM (PiXy!)

7 Pasting to the little clip board with the W worked great, but even though I clicked the icon on the top field, the text appeared in the field below.  I then copied it from there and pasted on top. 

Why are there two fields for posting?

Help.  I still can't figure out how to name a category for posts.

Posted by: erp at April 16, 2007 08:50 PM (9oHan)

8 Hi erp!

The second field is for extended entries when you don't want the whole post visible. You can start the post in the upper box, and finish it in the lower one. When you do this, the system generates a "more" link that takes readers to the conclusion. Look at the post "Requested (?) screenshot" (only post dated Sunday) on my page to see how it works. (Can't demonstrate this by linking directly, because direct links show the whole post.)

The "more" won't appear if you don't put anything in the lower box.

Category is selected with the "category" selector under the title box on the edit page. If you haven't created any categories yet, your choices will be "..." and "Example". You create new categories on the "Folders" page. More info in RocketJones's howto post here. Cheers!

Posted by: Old Grouch at April 17, 2007 12:26 AM (N7blS)

9 Thanks, Old Grouch!  And RocketJones too.

Posted by: Pixy Misa at April 17, 2007 01:32 AM (PiXy!)

10

Hi!

 

Since last night, I`ve gotten an internal server error when I click on the View button.  Is this a known problem, or something endemic to me?

Posted by: Timothy Birdnow at April 23, 2007 11:56 AM (+OCMQ)

11

In fact, here is the page they are sending me:

 

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last): File "/usr/local/lib/python2.5/site-packages/cherrypy/_cprequest.py", line 342, in respond cherrypy.response.body = self.handler() File "/usr/local/lib/python2.5/site-packages/cherrypy/_cpdispatch.py", line 15, in __call__ return self.callable(*self.args, **self.kwargs) File "Minx.py", line 60, in index return Page.go(cherrypy) File "/backup/test/minx/Page.py", line 446, in go Template.go_index(page) File "/backup/test/minx/Template.py", line 1842, in go_index page.content=do_template(page,t) File "/backup/test/minx/Template.py", line 173, in do_template return do_template_text(page,t) File "/backup/test/minx/Template.py", line 235, in do_template_text elif ttype=='here': s=show_here(page,opt,handler) File "/backup/test/minx/Template.py", line 63, in show_here return handler(page,opt) File "/backup/test/minx/Template.py", line 506, in show_entries text+=show_entry(page,template) File "/backup/test/minx/Template.py", line 516, in show_entry text=do_template(page,template) File "/backup/test/minx/Template.py", line 173, in do_template return do_template_text(page,t) File "/backup/test/minx/Template.py", line 229, in do_template_text text+=show_tag(page,opt,tags) File "/backup/test/minx/Template.py", line 99, in show_tag text=Filter.bbcode(text,tags=val[2],restrict=()) File "/backup/test/minx/Filter.py", line 365, in bbcode if opt[0]=='"' and opt[-1]=='"': IndexError: string index out of range Can you be of any assistance?

Posted by: Timothy Birdnow at April 23, 2007 12:00 PM (+OCMQ)

12 Sorry about that!

Looks like the error checking in the updated BBCode module is having a problem with something on your site.  I'll get that fixed right away.

Posted by: Pixy Misa at April 23, 2007 01:53 PM (PiXy!)

13 Your site is back now.

Sorry again about that error!  I think you have a slightly misformatted BBCode tag somewhere - maybe even in a comment - but that shouldn't have caused an error anyway.

Posted by: Pixy Misa at April 23, 2007 02:01 PM (PiXy!)

14 Wow, and now we're stuck in italics!

I didn't think that was possible!

Posted by: Pixy Misa at April 23, 2007 02:02 PM (PiXy!)

15 Ah, better now.

Thanks!  You found two bugs in the BBCode parser today.

Posted by: Pixy Misa at April 23, 2007 02:10 PM (PiXy!)

16
I added a new blog to my blogroll, and now the whole thing has disappeared! Also, my site only shows posts going back to yesterday.  Any suggestions?
I think these two are related. Hang on a tick...

Hmm.  Something in the comments on your American Pravda post seems to be breaking the page.  I'll get that fixed.

Also, could you tell me how to inbed a link, and how to use bold and italics?  My toolbar doesn`t seem to be working.
The easiest way to do this if the editor doesn't work for you is to use BBCode: documentation here.

What browser are you using?  I know there are some issues with the editor in Opera, but it at least partly works; I understand it doesn't work at all in Safari.

Posted by: Pixy Misa at April 24, 2007 03:13 PM (PiXy!)

17 Aha!  I found the problem.

One of the comments had a BBCode table tag - probably inadvertent - and no closing tag.  The BBCode parser is supposed to automatically fix that for you, but the closing tag was missing from my definitions.  I've fixed that (and a couple of other tags with the same problem), and your blog is back to normal.

Posted by: Pixy Misa at April 24, 2007 03:40 PM (PiXy!)

18

What I think might be a bug:

I tried copying some text out of FrontPage and pasting it into the composition box here, and the formatting came with it, which was really nice.

However, I had a couple of paragraphs which began with <p align="center">. In the composition box, they were centered, and when they were clicked, the "center" button highlighted, indicating that it thought they were centered.

However, when the page was posted, they displayed left justified.

I ended up looking at the page source, and it seems that in order for center justification to work properly the paragraph tag has to include style="TEXT-ALIGN: center"

Which is fine. The bug is that when the raw source included the align="center" tag but not that style tag, the composition window recognized it as being centered and displayed it centered, even though it didn't end up being centered in the ultimate post. Either the composition window should not recognize the align tag, or else the align tag should work in the real post.

My guess would be that in the real post, the align center tag is being overridden by CSS, whereas in the composition window it is not.

Posted by: Steven Den Beste at May 18, 2007 06:36 AM (+rSRq)

19 I would have thought that the align option would override the CSS, but I haven't actually tried it; and it may be browser-dependent or dependent on the surrounding page elements.

Posted by: Pixy Misa at May 18, 2007 04:23 PM (PiXy!)

20

Small formatting problem can be seen here. I included a fairly long section of text inside of a "spoiler" tag at the very end of the "more" section, and it correctly shows up as a button.

When I click the button, the new text shows up. But it lays on top of the comment entry section. The length is such that it overlays all the header area where name/email/website should be entered. It isn't shoving everything down when it opens.

Note that there's nothing at all after the spoiler close. I have a suspicion that if I tossed in one more line of text after it then it would work normally, but I don't want to change what's there now for fear of losing the demonstration of the bug.

Posted by: Steven Den Beste at May 26, 2007 12:16 AM (+rSRq)

21 Hmm.  Works in Firefox, broken in IE.  How unusual...

I think I know what might be causing it; there's some CSS in the comment form that could be confusing IE here.  I'll see what I can do.

Posted by: Pixy Misa at May 26, 2007 03:57 PM (PiXy!)

22 Pixy, I have a rather urgent need to have you ban someone for me. Details in email I've sent you.

Posted by: Steven Den Beste at May 28, 2007 01:59 AM (+rSRq)

23 Since I marked that one comment "hidden", instead of outright deleting it, I noticed something else odd. As I write this my main page shows 8 comments for that thread, but there's only seven. The hidden one is still included in the count.

Posted by: Steven Den Beste at May 28, 2007 02:28 AM (+rSRq)

24 Yes, the count doesn't reflect hidden and junk comments properly.  This will get fixed.

And your unwanted guest has been booted.

Posted by: Pixy Misa at May 28, 2007 02:48 AM (PiXy!)

25 There may be some sort of security problem having to do with the comment header fields. Two different people have reported finding someone else's name/web/email in the form when they went to it. (See this, for instance.) I myself haven't seen that happen, but I have my own cookie already.

Posted by: Steven Den Beste at May 29, 2007 01:01 AM (+rSRq)

26 Thanks Steven.  I saw this once before, but couldn't duplicate it or work it out from the code, and haven't seen it happen live.

This time it only took five minutes to find.  Funny how that works...

Posted by: Pixy Misa at May 29, 2007 01:59 AM (PiXy!)

27 You have a serious bug with URL collisions.

Posted by: Steven Den Beste at May 30, 2007 06:45 AM (+rSRq)

28

When I have images in the "more" section, then if I click the <> symbol to look at the direct HTML and then exit that popup, all images I had switch from being displayed correctly to IE7's box-with-red-X placeholder that indicates "image file not found".

When, a couple of times, I have used that popup to enter the img tags, they all displayed that same X-box.

But in all of these cases, when I publish, the images show up correctly.

Posted by: Steven Den Beste at June 02, 2007 02:59 AM (+rSRq)

29

The main entry section has the same issue.

Here's how to reproduce the problem:

1. Enter an image in your post.

2. Press the "<>" button to open up the direct HTML version.

3. Close the HTML popup either with "cancel" or with "OK".

Afterwards the images all become "cannot find" placeholders.

Posted by: Steven Den Beste at June 02, 2007 03:40 AM (+rSRq)

30 Oh, that wacky editor and its image paths.

Yeah, that's a known problem (known by me, at least), but the reproducible test case is valuable.

Posted by: Pixy Misa at June 02, 2007 12:40 PM (PiXy!)

31

Is the "statistics" function supposed to be enabled now? I see that the "coming soon" asterisk is gone from that entry in the main menu, and you mentioned last week that you were going to include it in the next major release.

But when I click it, I reroute to the main menu again.

For whatever it's worth, "export" is also not there.

Posted by: Steven Den Beste at June 05, 2007 06:56 AM (+rSRq)

32 Yeah, statistics is definitely supposed to be working.  I'm looking into that; there's something set wrong, but not for everyone.

I was about to upload the export templates, then things started blowing up and I had to handle that first.  That will be in place tomorrow.

Posted by: Pixy Misa at June 05, 2007 12:05 PM (PiXy!)

33 Another problem on the edit page.
Go to Content -> Comments

#1: Probably WOD, but I notice very old comments don't appear in the list. Is there a time restriction?

#2: Click on the "Page=2" link (to what would be a blank page) and get error message:
The server encountered an unexpected condition which prevented it from fulfilling the request.
Traceback (most recent call last):
File "/usr/local/lib/python2.5/site-packages/cherrypy/_cprequest.py", line 342, in respond cherrypy.response.body = self.handler()
File "/usr/local/lib/python2.5/site-packages/cherrypy/_cpdispatch.py", line 15, in __call__ return self.callable(*self.args, **self.kwargs)
File "Minx.py", line 111, in default return Page.go(cherrypy)
File "/var/minx/live1.0/Page.py", line 445, in go Template.go_index(page)
File "/var/minx/live1.0/Template.py", line 2120, in go_index page.content=do_template(page,t)
File "/var/minx/live1.0/Template.py", line 174, in do_template return do_template_text(page,t)
File "/var/minx/live1.0/Template.py", line 236, in do_template_text if ttype=='block': (s,i2)=show_block(page,t,i,opt,handler)
File "/var/minx/live1.0/Template.py", line 47, in show_block if ok: text=do_block(page,tsub,opt,handler)
File "/var/minx/live1.0/Template.py", line 57, in do_block return handler(page,opt,template=k0+'.template')
File "/var/minx/live1.0/Template.py", line 706, in show_comments page.Sql(query,args)
File "/var/minx/live1.0/Query.py", line 26, in do_sql perform_sql(page,query,vars)
File "/var/minx/live1.0/Query.py", line 55, in perform_sql c.execute(query,vars)
File "/usr/local/lib/python2.5/site-packages/MySQLdb/cursors.py", line 148, in execute query = query % db.literal(args)
TypeError: not enough arguments for format string
(Linebreaks stuck in by hand, so may not be exact!)

Posted by: Old Grouch at June 05, 2007 07:25 PM (KyCzn)

34 Ouchie.

Yep, happens every time. I'll get that fixed right away.

Posted by: Pixy Misa at June 06, 2007 04:54 PM (PiXy!)

35 Fixed now.

Posted by: Pixy Misa at June 07, 2007 03:00 AM (PiXy!)

36 I don't want to nag, or to keep harping on something that you just haven't had time to get to (this week having been a bad one, for instance) so just this request: When you think you have statistics working, please say so. Until you do, I'll continue to assume it's on your "Things to do that I haven't gotten to yet" list.

Posted by: Steven Den Beste at June 07, 2007 10:04 PM (+rSRq)

37 Will do, Steven.

Posted by: Pixy Misa at June 08, 2007 12:18 AM (PiXy!)

38 They switched our routing back again, so it isn't going through Level3 any longer, and I'm back to having a high rate of dropped packets.

Posted by: Steven Den Beste at June 13, 2007 04:26 AM (+rSRq)

39

Hi Pixy!

I have a regular commenter on my site from Germany who is complaining that his comments aren't getting through, but are being flagged as "awaiting moderation".  He's getting on me about it, so I thought I would ask you what is happening. I am set up for unlimited comments.  I assume this is some sort of spam filter?

Any input would be appreciated.

Thanks!

Posted by: Timothy Birdnow at May 08, 2010 02:09 PM (vhA+2)

Hide Comments | Add Comment

Comments are disabled. Post is locked.
32kb generated in CPU 0.03, elapsed 0.0334 seconds.
32 queries taking 0.0106 seconds, 91 records returned.
Powered by Minx 1.1.6c-pink.