ansonphong / postworld

Wordpress Theme Development Framework
GNU General Public License v2.0
7 stars 0 forks source link

Comments not being assigned post_id #78

Closed ansonphong closed 10 years ago

ansonphong commented 10 years ago

Hi Michel, I was testing the comments now and I noticed that when making a comment, and replying to comments, everything is working fine. Except, that when I reload the page, the new comments don't appear. So when I look in the database, this is clear that the comments aren't being assigned a comment_post_ID

image

You can see that replies are being attributed a parent comment ID, though replies also don't have a comment_post_ID.

image

This happened since we implemented the post="post" attribute functionality.

michelhabib commented 10 years ago

Phong, it looks like postworld plugin is working off a minified version of js, is there anything i need to run while developing? i am not very familiar with grunt, do i need to run something?

michelhabib commented 10 years ago

did you fix it? i checked a couple of posts, the comments are saved successfully to the right post? i tried it both locally and on staging.reality sandwich using the innuva user account. example here: http://staging.realitysandwich.com/feature/art_hand_analysis/

ansonphong commented 10 years ago

It's ok, you don't need to run grunt - although I recommend using it in the future - it only took me about 30 minutes to get fully implemented. This is my first time using it - very helpful app.

All you need to do is go into where you include postworld_includes() and change that to : postworld_includes('dev')

since postworld_includes('deploy') is the default

ansonphong commented 10 years ago

oh yes, I see the post by 'innuva' so it seems to be working. that's strange --- good news though. I'll try and look deeper into it. that was easy. it could be a bug on my local host.

michelhabib commented 10 years ago

thx for grunt, i will learn later to use it, must be very useful for deployment :) as for the bug, i traced back the ajax to make sure it returns the post id correctly. one possible explanation, could it be related to anonymous posts? although the screenshot above indicate that there is a logged in user.