Subarist's Comments
-
-
Also happens when setting summary display, if it has illegal syntax.
The articles in this test tag are all articles created in flarum. Just copying HTML articles from other websites and pasting them seems to cause the same error.
-
-
Support
- CSS and JS not rendering
Answer 
Make sure permission to set "WWW"
-
-
The reason for this problem seems to be that I skipped the XML check and imported a database text that doesn't comply with the specified format.
I believe that the issue arises when the invoked text does not comply with XML formatting.
When I imported a database text that adhered to the specified format, the search function worked flawlessly.
Searching for English words produced accurate results, and UTF8 characters were no display as expected.Is there a straightforward method to disable the XML check when invoking the search function?
It seems that this problem doesn't occur in Flarum. -
Note: The configuration and execution of the conversion process itself are actually quite simple.
In my case, the data specification of the database is quite messy, which resulted in continuous errors during the conversion (phpbb & discuz) process.
The reason is that the content of the database fails the "isValidXML" check.
I tried replacing obvious syntax errors in the database, such as "</br>" and "<br/>" as mentioned earlier.
However, dealing with these issues in over 50K articles proved to be too difficult. The variety of non-compliant code drove me crazy.
Another consideration is that after modifying the database, many older articles will lose their distinctive bbcode？ features (which are still presented uniquely on Flarum).
Approximately 99.99% of the entire database consists of articles in this peculiar format, and there are very few newly generated articles after migrating to Flarum. So, I decided to try skipping the check and directly import all the data.
importDiscussionsAsPosts / importPostsAsComments 'parsed_body' => $row->content
After the import was completed, I discovered that most of the articles only had titles in their first posts, losing the main content. It was then that I realized that due to the conversion from phpbb & discuz to Flarum, there might be some differences in the formatting of the old conversion program. As a result, all my discussions were missing the "first_post_id," which is crucial for the new style of display in Waterhole. However, it appears normal in Flarum because the hero title is present, followed by the posts.
Just when I was about to give up, ChatGPT suggested that I try rebuilding the "first_post_id":
After several hours of hardship, various attempts, and encountering errors, I have achieved some results that I hope won't pose major issues. Now, I can start verifying the other functionalities.
中文測試需求< -- pointless, just to test the UTF8 search ability
-
In reply to
Toby
Toby
Waterhole
Founder
May 27, 2023 It looks like many of the posts in your Flarum table contain closing </br> tags, in the absence of an opening <br> tag. This is invalid XML and doesn't make sense – they should be self-closing <br/> t...My database is integrated with PHPBB and DISCUZ, and it contains many outdated or customized code syntax.
After several rounds of merging and migrating to FLARUM, there may be some issues.Now, following the hint, I replaced "</br>" with "<br/>":
Currently, no errors are being thrown, and I think we will know in 40 minutes...
-
After approximately 40 mins, it was completed.
Error importing comments #573211: DOMDocument::loadXML(): Opening and ending tag mismatch: t line 1 and br in Entity, line: 1 Error importing comments #573212: DOMDocument::loadXML(): EntityRef: expecting ';' in Entity, line: 1 Error importing comments #573213: DOMDocument::loadXML(): Opening and ending tag mismatch: t line 1 and br in Entity, line: 1 Error importing comments #573216: DOMDocument::loadXML(): Opening and ending tag mismatch: t line 1 and br in Entity, line: 1 Error importing comments #573217: DOMDocument::loadXML(): Opening and ending tag mismatch: t line 1 and br in Entity, line: 1 Error importing comments #573223: DOMDocument::loadXML(): Opening and ending tag mismatch: t line 1 and br in Entity, line: 1 537738/537738 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%Comparison to the size of the data table, it appears that there are many missing entries.
flarum：
waterhole ：
flarum_posts & waterhole_comment ：
User data was entered, but unable to log in. Is it necessary to change the password?
-
In reply to
Toby
Toby
Waterhole
Founder
May 27, 2023 Does the progress bar ever move beyond zero? Do you mind pasting a sample of your Flarum comment data for the failing comments (specifically the content column) here, or email it to toby@waterhole.dev...In fact, I noticed that the the database is changing.
The progress bar is also increasing.
So, I have decided to let it run until completion and see what happens.
I think it will take some time.
-
When set to 0.1.x-dev, the update was successful.
Now stuck at "Importing 537738 comments..."
-
Unknowingly, I just happily spent an hour playing around on a newly set up Waterhole.
Although I may not be able to afford the $299 price, I genuinely feel that it could be worth it.
At first glance, it resembles Flarum, but the experience feels completely different.
Every detail is filled with creativity and ideas. It's a brand new design that has been thoroughly thought out.
The setup is not as mature and convenient as Flarum's backend, but the level of customization could be higher.
I'm not a coder, just a simple user.
Maybe it's not ready for widespread use with localization yet.
I just want to express that I really love this groundbreaking new forum—it's truly different.
You'll know once you try it.
By ChatGPT ^^
-
In reply to JoshJosh
May 26, 2023 I don’t want to be that guy but can I maybe suggest making a post for it in the support channel? That way others can find it if they have the same issue and it stops this thread from getting cluttered...Of course, no problem. completely understand.
-
In reply to
Toby
Toby
Waterhole
Founder
May 26, 2023 Oops, I forgot to submit it to Packagist. Should be working now![root@instance20220311042805 forum]# composer require waterhole/import In PackageDiscoveryTrait.php line 331: Could not find a version of package waterhole/import matching your minimum-stability (stable). Re quire it with an explicit version constraint allowing its desired stability. -
In reply to
Toby
Toby
Waterhole
Founder
May 26, 2023 Oops, I forgot to submit it to Packagist. Should be working now!I'll try it later...
Anyway, I proceeded with a clean installation, and it went smoothly.
-
In reply to
Subarist
Subarist
May 26, 2023 I was quite happy to have my question answered by a legendary figure. I have a relatively inactive Flarum and I think I'll perform a test migration to see how it will look on Waterhole. We are a non-...In the "Migration Steps," error while executing "composer require waterhole/import."
[root@instance20220311042805 forum]# composer require waterhole/import Do not run Composer as root/super user! See https://getcomposer.org/root for details Continue as root/super user [yes]? yes In PackageDiscoveryTrait.php line 368: Could not find a matching version of package waterhole/import. Check the package spelling, your v ersion constraint and that the package is available in a stability which matches your minimum-sta bility (stable). -
In reply to
Toby
Toby
Waterhole
Founder
May 26, 2023 From the Software License: > Free Trial: Any person may use the Software in an environment that is purely for the purposes of development and client preview, and only accessible by a restricted numbe...I was quite happy to have my question answered by a legendary figure. I have a relatively inactive Flarum and I think I'll perform a test migration to see how it will look on Waterhole. We are a non-English speaking community, and I believe it will take some time before we can use it in actual production. However, it seems that Waterhole already has the basic elements that I believe a forum should have at the moment. It's just for fun and curiosity, so I'll give it a try.
Search function reported an error---fixed
summary display error --- fixed
Case closed after upgrade to 0.2.0