Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] e107::getComment()->render() not ready to display mutiple times on same page #1944

Closed
nesjett opened this issue Oct 19, 2016 · 19 comments
Labels
Help Wanted type: bug A problem that should not be happening
Milestone

Comments

@nesjett
Copy link
Contributor

nesjett commented Oct 19, 2016

As the tittle says, It seems that if you call reder() multiple times on the same page, It´s default behaviour will be broken.

It adds the comment as espected, and renders them, but the javascript is not done in the right way and it shows the resulting new comment on the wrong element.

Explanation:
The problem is that you handle a lot of things with ID in order of using Classes and find them trought parent (or somthing dynamic)

Scenario:
We would need a lot of comment forms on a social news feed, for example like facebook one.

I´ve already solved that, but I´m still working on making prev next buttons work, and edit one

Ill make a pull request when finished, hope it helps.

@nesjett nesjett changed the title [bug] e107::getComment()->render() not ready to display mutiple times on same page [bug][enhancement] e107::getComment()->render() not ready to display mutiple times on same page Oct 19, 2016
@nesjett nesjett changed the title [bug][enhancement] e107::getComment()->render() not ready to display mutiple times on same page [bug] e107::getComment()->render() not ready to display mutiple times on same page Oct 19, 2016
@nesjett
Copy link
Contributor Author

nesjett commented Oct 19, 2016

Update: Im driving crazy with next prev buttons, can someone confirm that they are working as expected? (in my case they just doesnt do nothing)

Fix -> #1945

@Moc Moc added the type: bug A problem that should not be happening label Oct 19, 2016
@Moc Moc added this to the e107 2.1.8 milestone Feb 28, 2018
@Moc Moc assigned CaMer0n and unassigned CaMer0n Feb 28, 2018
@Moc
Copy link
Member

Moc commented Jun 26, 2018

@nesjett Have you been able to solve this?

@Moc Moc modified the milestones: e107 2.1.8, e107 2.1.9 Jun 26, 2018
@CaMer0n CaMer0n modified the milestones: e107 2.1.9, e107 2.2.0 Aug 22, 2018
@CaMer0n
Copy link
Member

CaMer0n commented Apr 11, 2019

@Moc @nesjett @Jimmi08 @SimSync This commit above is a partial fix that hopefully won't break the comments. If you guys can test my changes thoroughly over the next 48 hours, that would be very helpful. I have tested locally, and haven't found any issue so far.

@Moc
Copy link
Member

Moc commented Apr 12, 2019

So far, adding comments still seem to work. Haven't tested with multiple comment forms yet.

@Evgura
Copy link

Evgura commented Apr 12, 2019

@CaMer0n The whole structure of the comments was broken. Maybe because of CSS or Javascript.
Rolled back the update.

@Jimmi08
Copy link
Contributor

Jimmi08 commented Apr 12, 2019

Hi all,
I don't know what to test because I hadn't any problem with comments (except the position of new reply comment with nested comments)

before update:
So I added nested comments to news, no problems, I changed setting to set nested off, I got paginated comments, button prev and next works.

I updated
Everything looks normal, both nested and not nested.
I only noticed a bit slow reaction on next,prev buttons but it can my installation itself.

I added comment menu to news sidebar...
everything works

It surprised me that Moderate comments took me to admin area...

Ok, I maybe have the problem:

  • single news

  • click on reply - works, the position of reply is fixed now

  • click on reply on another comment - no reaction
    after refresh, I can reply, but it takes visible time to display textarea (again it could be my problem)

  • I can open more reply textarea at once after refresh... just note, maybe it's ok.

  • I have set Comment sorting - newest at first, but if I am on next page (not first), and a new comment is posted (not reply, first level comment), it's not visible, you need to manually click on pagination...

@CaMer0n
Copy link
Member

CaMer0n commented Apr 30, 2019

@Evgura Did you try clearing the browser cache after updating?

@Evgura
Copy link

Evgura commented Apr 30, 2019

@CaMer0n Yeah, I cleared my browser cache. It doesn't help.
That such nonsense is obtained.
9966332211

Comments should look like this:

996633221199

@CaMer0n
Copy link
Member

CaMer0n commented Apr 30, 2019

Thank you @Evgura . Would you be okay to send me your theme (via Private message on Github) so I can test with it?

@Evgura
Copy link

Evgura commented Apr 30, 2019

@CaMer0n , Don't know how to github to send a personal message, theme BS_Magazine_02, I have the theme without any changes.

@CaMer0n
Copy link
Member

CaMer0n commented Apr 30, 2019

okay, thank you @Evgura . I'll just download it then.

@Jimmi08
Copy link
Contributor

Jimmi08 commented Apr 30, 2019

@Evgura theme from e107.org or from Fizi site?

@Evgura
Copy link

Evgura commented Apr 30, 2019

@Jimmi08 The website fizi I can not open the theme site e107.org
Also, I tried to put the theme of website with repository fizi on Github. The same result.

@Jimmi08
Copy link
Contributor

Jimmi08 commented Apr 30, 2019

@Evgura just posted you fix by mail you have on my site. Test and you can close this. This is the theme update problem, so the theme author needs to do it.

CaMer0n added a commit that referenced this issue Apr 30, 2019
…eme must be changed to .comments-container
@Evgura
Copy link

Evgura commented Apr 30, 2019

@Jimmi08 Rename it "style" ?

@CaMer0n
Copy link
Member

CaMer0n commented Apr 30, 2019

@fizi @Evgura @KiraTheUltimate All references (eg. in style.css) to #comments-container need to be changed to .comments-container

@Jimmi08
Copy link
Contributor

Jimmi08 commented Apr 30, 2019

@Jimmi08 Rename it "style" ?

no, just upload. it's the way how to customize a theme without losing of the update feature

@Evgura
Copy link

Evgura commented Apr 30, 2019

I tried to change #comments-container to .comments-container and nothing has changed.
Uploaded file Jimmi08, all became well.

@CaMer0n CaMer0n modified the milestones: e107 2.2.0, e107 2.2.1 May 4, 2019
@CaMer0n CaMer0n modified the milestones: e107 2.2.1, Future May 27, 2019
@Moc
Copy link
Member

Moc commented Oct 3, 2019

I am assuming this is fixed (when themes apply the right styling)

All references (eg. in style.css) to #comments-container need to be changed to .comments-container

@Moc Moc closed this as completed Oct 3, 2019
@Moc Moc modified the milestones: Future, e107 2.2.2 Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help Wanted type: bug A problem that should not be happening
Projects
None yet
Development

No branches or pull requests

5 participants