thread title/ short content description
chapter 1 title
chapter 1 full = title 1 + list of post 1.1 ... 1.m1
chapter 2 title
chapter 2 full = title 2+ list list post 2.1 ... 2.m2
...
chapter n title
chapter n full = title n + link list post n.1 ... n.mn
Note:
in this window I prepare the indexes for Arrancar's artwork, see http://lah.li/p/315436 for the last one posted so far and http://lah.li/p/267270 for the first one. Until now they were mere link lists. Below I try a different style - avoiding problems like inadvertantly creating spoilers inside links, or links inside links, etc. - by using clickable 's mimicking the very small arrow http://lah.li/templates/AcidTechTiger/images/post_old.gif that our lah.li site uses as "pointer" on many webpages. Simplified version until http://lah.li/p/317665 has landed -->
----------------------------------------------------------
Index One-Chapter Works (click on any arrow ==> jump to corresponding post)
And I Ran Away November 2011: Shota
A boy runs away from home, and his sister goes looking for him
She finds her brother in the forest, and notices him without clothing
The boy feels ashamed of his body. His sister shows him there is nothing to be ashamed of
The girl notices her brother becoming very excited. She tries to tell him not to release his seed inside her
The boy was overexcited and almost comes inside her. His sister begs to be covered in his seed and the boy releases.
The girl then promises to help her brother with his urges, and the two return home with the moonlight guiding them.
A True Friend May 2012: Futanari
A high school girl begins to wonder if there is ever anything to do in town anymore
Saya encounters Hitomi and decides to confront her yet again
Saya was able to obtain a video tape of Hitomi. She has no choice but to go to Saya's place and watch it with her
Saya wants to see all of Hitomi's body. She removes some of Hitomi's clothes and takes some photos of her
Satisfied to see Hitomi covered in her own seed, Saya then allows Hitomi to use the shower while she decides what to do next
Hitomi tries to figure out how Saya knows so much about her. She plans to confront Saya with her conclusion
Hitomi was correct about Saya being a Futanari. Hitomi was always embarrassed about being a futa herself, but now, thanks to Saya, she is proud of her body
Hitomi tells Saya how good it feels, and lends a helping hand. Saya gives Hitomi all of her seed.
Saya is glad Hitomi could see that being a Futanari is nothing to be ashamed of. Even though she was a bit cruel to her to accept the truth, Saya really was a true friend to Hitomi.
Study Day November 2012: Loli, Yuri
It's the end to another day at school for Harumi, Emilia, Naomi and Sora
Harumi wants to know more about what they learned. Naomi decides to ask Emilia for more information
Emilia begins to explain more about what they learned in school. Harumi becomes part of her demonstration and her body is exposed in front of her friends
Harumi is still feeling uneasy. Emilia helps her feel more at ease and removes her clothing. Naomi and Sora soon follow
Emilia uses one of the "tools" to help Harumi reach the highest level of pleasure
After watching Harumi reach the highest level of pleasure, Emilia is unable to hold back and starts to reach the same level as Harumi with the help of her sister's toy
Exhausted from her first climax, Harumi watches her friends reach the highest level of pleasure.
Harumi is thankful for being able to experience the pleasures of her body. Emilia stays atop the roof while Sora and Naomi become very close friends and return home together.
Tears of Love Valentine 2013: Yuri love story
Two best friends Natsumi and Akane are returning home
Natsumi was able to open up to Akane and tell her that she loves her
Akane kisses her gently and the girls remove pieces of their clothing
Natsumi is still feeling very shy and Akane helps her feel more comfortable
Natsumi was able to give all of her love to Akane and the two of them climax together.
Akane was able to get Natsumi to smile and believes she was told she loved her at the right time. They return home and spend their days in happiness.
Futaba Academy March 2013: Futanari
It's the first day, and the instructor asks everyone to introduce themselves
The day continues on like normal as the girls begin their classes
At the end of the day, everyone is asked to gather around. Thinking they were the only Futanari in the class, Yutaka reveals the secret of the academy and each of the student's find out they have much more in common
Everyone is issued a condom and gets ready for the after school activities. Yutaka is glad to see everyone getting along
Some students pair up while the others observe and await their turn
The other students are able to pair up and switch places
The students begin to feel the ultimate pleasure
Everyone begins to climax almost at the same time.
Yukata takes a class photo and is convinced that this will be another great year at Futaba Academy.
Under Her Spell June 2013: Loli, Tentacles
A girl enters the forest
The girl is convinced it's a normal forest and feels at ease until she hears a voice
According to Phoebe, Angela is learning Dark Magic. She doesn't listen and continues to show more of what she learned
Angela loses control of herself while the vines continue to explore Phoebe's body
The vines continue to multiply and becomes to much for Phoebe to handle
As more vines enter Phoebe's body, Angela decides to feel the pleasures of the vines as well
The seed of the vines is released as Phoebe and Angela climax together
The girls become very close friends and agreed to meet again another day. As they leave the forest...
A girl of incredible power appears in the forest and plans to confront Angela for using those spells
After a moment of sibling rivalry, Angela finally says she's tired of her older sister Nadia always bossing her around
Nadia uses her own set of spells to punish Angela. Using the Vines of the Underworld on Phoebe has left her fatigued and stood no chance against her sister's spells.
Nadia later confesses that she is proud of her little sister on learning those spells at such a early age. The two return home with their beautiful bodies exposed to the night sky.
_________________ My avatar shows the first encounter of Yuki in the Land of Eternal Snow. Yuki would become my favorite character in the on-going Mystics Saga by arrancar85
Last edited by jacxxx on Mon Mar 17, 2014 9:11 am; edited 24 times in total
_________________ My avatar shows the first encounter of Yuki in the Land of Eternal Snow. Yuki would become my favorite character in the on-going Mystics Saga by arrancar85
Last edited by jacxxx on Thu Dec 20, 2012 11:04 pm; edited 9 times in total
I found out when I tried to give a link from the first post of p54 to the last post of p53 (these two posts are closely connected)
Wanted: a robust solution for our page break problems, it's now quite time consuming and not as good as I like.
_________________ My avatar shows the first encounter of Yuki in the Land of Eternal Snow. Yuki would become my favorite character in the on-going Mystics Saga by arrancar85
You can't link to my first post through its post ID because that post was supposed to be in this page, I edited its post time to display in the first post of the first page though. That is not something that we do very often - technically, only Sat and I have the ways to screw up things like this -, I could fix that by switching the post ID to an unused one previous to Elec's post, but I guess that's unnecessary as you can link to it through the thread id as you did above: http://lah.li/forum/viewtopic.php?t=25700
jacxxx:
ult_combo: ... I have the ways to screw up things like this ...
I'm not an expert but it looks like your corrupting the data base with an extremely dirty trick here
Playing with a fresh loli looking db satanic fruit like this may feel pretty exciting, but it may also be highly dangerous for future software upgrades, changes, ... --> it should be forbidden
Crescent: Not really, editing post time is minor and is done almost every time when merging threads.
ult_combo: ^ Exactly. Post time is merely a number representing the timestamp of the post, it doesn't matter if I set it to 2 days ago or 1980.
The only issue here is that the module to display posts orders them by post time, while the module to seek posts uses post IDs for ordering. Both of these are analogous 99.9998% of the time, except when we edit it manually. Sure thing, phpBB devs didn't intend for us to be doing that, but as there are no "post re-ordering" tools, we don't have another option as Crescent said.
jacxxx:
ult_combo: ... Sure thing, phpBB devs didn't intend for us to be doing that, but as there are no "post re-ordering" tools, we don't have another option as Crescent said.
I guess it would take you about 2 hours to make such a tool
Btw: on my PC I have set the snow to max - otherwise we'll have a gray and sluggish Xmas here
jacxxx:
ult_combo: ... Sure thing, phpBB devs didn't intend for us to be doing that, but as there are no "post re-ordering" tools, we don't have another option as Crescent said.
I guess it would take you about 2 hours to make such a tool
Btw: on my PC I have set the snow to max - otherwise we'll have a gray and sluggish Xmas here
jacxxx:
ult_combo: ... Sure thing, phpBB devs didn't intend for us to be doing that, but as there are no "post re-ordering" tools, we don't have another option as Crescent said.
I guess it would take you about 2 hours to make such a tool
Btw: on my PC I have set the snow to max - otherwise we'll have a gray and sluggish Xmas here
jacxxx:
ult_combo: ... Sure thing, phpBB devs didn't intend for us to be doing that, but as there are no "post re-ordering" tools, we don't have another option as Crescent said.
I guess it would take you about 2 hours to make such a tool
Btw: on my PC I have set the snow to max - otherwise we'll have a gray and sluggish Xmas here
ult_combo: I didn't analyze this part very throughout yet, but AFAIK there's no "single order" of posts - each post has data associated with it: a serial (integer auto-incrementing) ID, post timestamp, author etc.
Every time you request (open) a page, our server will fetch the data (posts) according to your request. Our default option (at bottom of the thread) is "Oldest First", in which the posts are ordered by post time ascending ("older" posts have a lower unix timestamp, but that isn't meaningful to this topic).
Now imagine if you'd request "Newest First", it'd do basically the same thing - in a layman's view: our backend would query the posts' table in a manner that fulfills your request as usual, but order the set of results (posts) according to the request parameters (newest post time first) and then slice this ordered set of results in sets of 15 which correspond to each page and finally serve you the page you requested.
ps. Of course, actually, the backend doesn't slice the result in different pages as that'd be just unnecessary extra processing. After ordering the result set, it simply offsets the start of the result set by the value passed in the "start" parameter and fetches it plus the next 14 posts in the thread, if these exist (note that the offset is 0-based). I think that the idea of slicing the results in pages is easier to grasp though and that's what the end-user sees in the end.
^ The paragraph above is how it goes for selecting a page in a thread, now for linking to a specific post things are a *little* tad bit more complex.
So, in short, ordering is done dynamically for each page based on your request.
jacxxx: On my old laptop I just used XP & chrome & snow on --> the snow moves much more regular in chrome than it does in opera --> I keep it on
To my remark
jacxxx: I meant a tool that doesn't mess up the db. Eg your start post gets the post id of elecs post, elec the next id and the last in the row gets the address that your startpost ... got ...
you first answered
ult_combo: Yeah, I thought about that, however, let's say you linked to a post before I edited a post's time in that thread, then your link would be linking to the wrong post.
which was exactly why I thought it might take you 2 hours instead of 2 minutes
I think you could have done the following: you make a new post with ID p1= http://lah.li/forum/viewtopic.php?p=288596#288596 - this happens to be the post ID of your welcoming post for the new winter theme. Before filling this post with your own content you are going to copy the content of the previous post, with post ID p2= http://lah.li/forum/viewtopic.php?p=288575#288575 - this is your last post before the welcome post. That's easy, even I could do that. But the difficult part is to find all the posts - if any - that contain the link p2 (the normal search doesn't work for post ID's ?!). Having found these, it seems relatively easy to change all these p2 into p1. After this we copy the content of p3 to p2, take care of the links to p3, etcetera, until you have doubled Elec's post, and did the last link repair on it. Only then would you be allowed to put your own content in the start post together with a fake time (e.g. Elec's time - 1 sec)
In your last post you very clearly explain "how it goes for selecting a page in a thread" but when it is going to be really exciting you only say "now for linking to a specific post things are a *little* tad bit more complex." I would like to know eg what happens when I try to open your post http://lah.li/forum/viewtopic.php?p=288596#288596 which I can only see here http://lah.li/forum/viewtopic.php?t=25700
jacxxx: (the normal search doesn't work for post ID's ?!)
Interesting find. I guess that's most likely because our search discards the special characters hence it doesn't find a match. Remind me to add it to the official bugtracker, when we have one.
Your logic is good, however there are some more complications to be thought of. Doing a complete text-based search in 239k+ posts would probably take a while - sure we have the Search option is which optimized and cached - but obviously some testing would be in order to ensure that it doesn't crash the server. Also, of course, editing multiple posts at once would seem suspicious to our extra security module, which means adding more exceptions. Let alone the overall process seems overly complicated for something so simple. I'm pretty sure there's an easier way around. Note that we currently have much higher priority projects in development, so this will probably take a long while for an official release. In fact, this should probably be an addon to the mods' thread split/merge tool, as changing thread OPs hardly has any other use.
I haven't had time to check the code for this part yet, however, it seems pretty obvious to me. Just don't write my words on stone
The "p=288596" part of the URL tells the server to fetch the page of (whichever) thread contains the post ID 288596. So then the server will find said post, check which thread it belongs to, fetch all posts belonging to said thread, order the results by post ID and then offset the start of the result set to something like
I wrote the formula above in JS so it can be easily debugged/demonstrated. Of course, a php version of that formula would use the floor() function to round down. I didn't check whether it is the actual formula being used, but one way or another, it just determines which page the post belongs to and offsets the start of the result set to the first post of that page, then displays it and the next 14 posts if these exist.
The hash part "#288839" is a browser mechanic that tells the browser to scroll the viewport down to the anchor of name/id "288839". As you probably already assumed, our server outputs these anchors in each rendered post to make them linkable. And when our backend fails to guess the right page number of the post due to the post id not being analogous to the post time, the browser doesn't find the name/id from the hash which isn't present in the rendered page and nothing happens.
edit: I've fixed the first post by switching its ID by an unused one previous to Elec's post, this way it doesn't break the linking to any other post and only affects my post which is now linkable. There are well over 30k unused IDs which are not only enough for a life time, but also the number increases by day with deleted spam and such making this a viable fix. There's now an alpha prototype of it usable by admins with db access, but I consider it overly hackish and unnecessary to be made into a feature for now. If demand doesn't increase, which probably won't, it will probably have a chance to become a feature after the major backend software upgrade which is being planned.
ult_combo:
jacxxx: (the normal search doesn't work for post ID's ?!)
Interesting find. I guess that's most likely because our search discards the special characters hence it doesn't find a match. Remind me to add it to the official bugtracker, when we have one.
Your logic is good, however there are some more complications to be thought of. Doing a complete text-based search in 239k+ posts would probably take a while - sure we have the Search option is which optimized and cached - but obviously some testing would be in order to ensure that it doesn't crash the server. Also, of course, editing multiple posts at once would seem suspicious to our extra security module, which means adding more exceptions. Let alone the overall process seems overly complicated for something so simple. I'm pretty sure there's an easier way around. Note that we currently have much higher priority projects in development, so this will probably take a long while for an official release. In fact, this should probably be an addon to the mods' thread split/merge tool, as changing thread OPs hardly has any other use.
I haven't had time to check the code for this part yet, however, it seems pretty obvious to me. Just don't write my words on stone
The "p=288596" part of the URL tells the server to fetch the page of (whichever) thread contains the post ID 288596. So then the server will find said post, check which thread it belongs to, fetch all posts belonging to said thread, order the results by post ID and then offset the start of the result set to something like
I wrote the formula above in JS so it can be easily debugged/demonstrated. Of course, a php version of that formula would use the floor() function to round down. I didn't check whether it is the actual formula being used, but one way or another, it just determines which page the post belongs to and offsets the start of the result set to the first post of that page, then displays it and the next 14 posts if these exist.
The hash part "#288839" is a browser mechanic that tells the browser to scroll the viewport down to the anchor of name/id "288839". As you probably already assumed, our server outputs these anchors in each rendered post to make them linkable. And when our backend fails to guess the right page number of the post due to the post id not being analogous to the post time, the browser doesn't find the name/id from the hash which isn't present in the rendered page and nothing happens.
edit: I've fixed the first post by switching its ID by an unused one previous to Elec's post, this way it doesn't break the linking to any other post and only affects my post which is now linkable. There are well over 30k unused IDs which are not only enough for a life time, but also the number increases by day with deleted spam and such making this a viable fix. There's now an alpha prototype of it usable by admins with db access, but I consider it overly hackish and unnecessary to be made into a feature for now. If demand doesn't increase, which probably won't, it will probably have a chance to become a feature after the major backend software upgrade which is being planned.
ult_combo:
jacxxx: I just had another interesting find: we can shoot each obnoxious lah-snow crystal out of the air with a well aimed mouseclick
Finally! I expected people to find it out in the first day.
jacxxx: It appears that the DB software sometimes is a black box for you as it is for me. It seems that you don't have access to it's source.
DB software source? But of course, it is a black hole draining the life force of any being that dares get in contact with it. Now if you're talking about how our backend conducts the queries to turn your requests into results, it is nothing but a well documented and very simple structured language.
jacxxx: A feature in the search function that I'd like to be changed is the following:
when you search eg p=288440#288440 (elec's 1st post in the current thread) you'll find only the post with that text on the current page, and not the same text on previous pages! This feature makes this kind of search very unuseful. I would hope to find all posts containing p=288440#288440 on every page and in each thread! (it appears in these previous posts afaik: http://lah.li/forum/viewtopic.php?p=288839#288839 and http://lah.li/forum/viewtopic.php?p=288517#288517 )
You mean this feature which already exists?
jacxxx: Related: Some time ago I asked for a trick to find all links to a specific image attachment. I now realize it could be done simply with the usual search added with extra delimiters? hm ... trying to find "find all links to a particular attachment" I now get error message ...
No idea how you managed to get a db error from searching. Provide steps to reproduce the issue so we can investigate if it repeats.
jacxxx: A less important detail of the search function: it does find eg hp?p=288440#288440 on this page but it does't find php?p=288440#288440
Tried just now and both found this thread.
jacxxx: It's looks fine to re-use redundant post ID's (the fact that you have these redundancies seems less satisfactory). And in this case you found quite an appropriate redundant one
But by the contrary! There's nothing redundant about these IDs, in fact, they are completely necessary for the well-being of our dear DB. Each ID is supposed to uniquely represent a single post. When one post is deleted or lost in a db crash, the ID is freed but never re-used by the DB software. It has be this way, otherwise if all post IDs were re-used, imagine if you link to a post in LAH Pictures section, then it gets deleted and the ID is reused by a post in the shota section. That's one of the reasons DBs have to uniquely identify each post. Obviously, re-using deleted IDs which have no data associated with it (which are the great majority of these deleted posts) doesn't affect the db egine nor forum software, but doing that for every deleted post would be asking to create reference issues sooner or later.
jacxxx:
ult_combo:
jacxxx: I just had another interesting find: we can shoot each obnoxious lah-snow crystal out of the air with a well aimed mouseclick
Finally! I expected people to find it out in the first day.
It crossed my mind some time ago that you could implement this, but ...
I never aimed to click a moving flake because it would be so apparently useless
I discovered it by accident: when I was hitting the search button a large snow flake happened to explode at the same time
ult_combo: ... When one post is deleted or lost in a db crash, the ID is freed but never re-used by the DB software. It has be this way, otherwise if all post IDs were re-used, imagine if you link to a post in LAH Pictures section, then it gets deleted and the ID is reused by a post in the shota section. That's one of the reasons DBs have to uniquely identify each post. Obviously, re-using deleted IDs which have no data associated with it (which are the great majority of these deleted posts) doesn't affect the db egine nor forum software, but doing that for every deleted post would be asking to create reference issues sooner or later.
I can see that clearly now
ult_combo: Update on the matter: Sat and me took a look on the issue. Thing is, the search id is not serial but rather randomly generated and there is currently no check to see if the randomly generated id is in use or not. I made the estimation that to reproduce the issue right now the odds would be 1 to 33554431.984375 searches, that is, ((2^31)-1)/64 where 64 is the number of searches being tracked at the moment.
I guess I'll fix that, even though it's virtually impossible to reproduce atm. I guess the original phpbb devs overlooked it due to the very slim odds.
Going off-topic a bit, or better, on-topic, could you please post a thread for each issue you find and would like fixed in the Help and Test forum? That way we can evaluate and analyse them much better, check if it is reproduce-able, decide whether to fix and its priority as well as tracking the overall progress much better. If you just post everything on a complete irrelevant topic - as you can see, this is the Winter theme announcement thread and not a bugtracker -, there are high odds that these issues will be missed/forgotten and not receive the proper attention and triage.
edit to reply the post above that jacxxx posted while I was writing this one:
jacxxx: Is the search button also well documented? One of my requests here was to find all posts with a link to the picture with id=1849 (it is viewed over 4000 times and the neigboring pics only 200 - 300 times). Why doesn't a simple search "id=1849" give any results? There should be at least one result - my old post is referring to "that old pic" which contains this id!
The search as a whole probably isn't - I hardly look at phpbb docs, rather I prefer to analyse the actual code. I can read it just as fast or faster than English text. The search module has over 2k lines, but breaking it into modules and isolating the issue makes it exponentially faster to read. And when I'm not entirely sure what one line means, I can look up the documentation for the given function, pretty much like reading a text with a dictionary help.
About the pic with 4k views, it is probably due to the pre-caching that was enabled for a long time - with pre-caching enabled, the first pic(s) of a page are automatically loaded every time you open the page, regardless of the user actually the seeing the pic or not. That generates fake view count. And I should add that right now I've re-enabled the pre-caching since the last boxed attaching viewing update, that's why the performance is better now. It will probably stay like that until the next lightbox update.
jacxxx: I mean, when I use that feature (I almost always display the results as "posts") I found only ONE result where I expected to find at least THREE results when searching for "p=288440#288440".
...
I tried it now again - with the posts display option on - and the result is different now (XP & Chrome): with (1) I now get 3 hits (the first one from the previous page) and with (2) I get 2 results (2 posts on the current page).
Possibly due to the search caching or our dictionary search/special chars replace/html-encoded chars or something else. Will take a look at that sometime.
jacxxx: Well, the search button gave such error messages all the time when I switched from searching post ID's to the search "find attachment". Closing the browser and restarting a couple of hours later things are back to normal now.
I don't get the "find attachment" part. We don't have an attachment search function yet AFAIK. Did you just put the urls of the attachment there and it was constantly giving the error? My investigation leads to 1/33554432 odds of that happening.
jacxxx: I can see that clearly now
Oh yeah, I was a little lazy to explain it. I used the linking analogy to demonstrate it, but then you could've said "nah you're just being lazy, why don't you just rewrite all posts that reference that post to '(deleted)' then", well, then we'd have a problem with the warnings' reference posts which we'd have to clear as we delete posts to don't link to the wrong posts, and of course, if we ever add any feature referencing posts it'd mean having to somehow reset the reference whenever a post is deleted and so forth, making it very costly performance-wise to delete a post and nevertheless to say, an almost unmaintainable scheme. So this unique ID pattern is a standard adopted by most if not all of the large relational db software.
ult_combo: Done. Do you want to move something else there or to a new thread before I wipe this page of the thread and half of the 2nd one? I'll probably do that tomorrow so you can backup the texts in case.
_________________ My avatar shows the first encounter of Yuki in the Land of Eternal Snow. Yuki would become my favorite character in the on-going Mystics Saga by arrancar85
Last edited by jacxxx on Fri Dec 28, 2012 10:40 am; edited 1 time in total
Our forum system doesn't support sub-spoilers. Btw you can also check how the BBCode tags will behave from the preview button.
I think it doesn't work because our current PHP BBCode filters/doesn't accept opening a repeated BBCode tag without closing it first. (example code below)
In other words, you can't open a spoiler inside another spoiler because our current PHP BBCode software automatically filters repeated unclosed tags.
Maybe Sat could take a look at that when implementing LAH's next PHP BBCode and add an exception for the spoiler tag?
Not that it is *EXTREMELY* needed, but it comes in handy in quite a few situations for maintaining long threads/posts organized.
_________________ My main MF acc was suspended, use other mirrors until I re-up it all to a new host.
There is no knowledge that is not power.
Our only limitations are those we set up in our own minds.
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
Measuring software productivity by lines of code is like measuring progress on an airplane by how much it weighs.
Programming is an art form, whose real value can only be appreciated by another versed in the same arcane art.
@ Jacxxx:
The page break issue is a result of me splicing a very corrupted database about 3 years ago.
It cannot be solved unless I manually run a crosscheck against every single post in on the site,
which cannot be solved on the live site. Another solution would be to completely delete the affected
threads...
@ult_combo:
I think these new BBCODE issues seem to be caused by implementing the magnet tag,
it seems to cause a few bugs. I currently have not found a solution for that,
but we need the magnet tags, especially as filehosters are dying en masse.
You are free to contact me on skype or gtalk and help me debug it if you find the time.
_________________ Some people say, the universe is a Star Ocean!
Want to donate to keep the site up? PM me for possible donation ways!
We now also accept Bitcoin.
Alright, since I'm on vacation I should have more than enough free time.
And yeah, the magnet tag is really important, I should resume my uploads to LAH's host machine soon enough (provided it still has enough HD space ).
_________________ My main MF acc was suspended, use other mirrors until I re-up it all to a new host.
There is no knowledge that is not power.
Our only limitations are those we set up in our own minds.
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
Measuring software productivity by lines of code is like measuring progress on an airplane by how much it weighs.
Programming is an art form, whose real value can only be appreciated by another versed in the same arcane art.
Sat: The page break issue is a result of me splicing a very corrupted database about 3 years ago. It cannot be solved unless I manually run a crosscheck against every single post on the site, which cannot be solved on the live site. Another solution would be to completely delete the affected threads...
This is very abstract language to me, Sat. Can you make it explicitly clear in simple terms in the example mentioned:
A different address has been assigned to each post a short time ago, but choosing any of the middle three addresses you jump to the first post of p54. How can your splicing 3 years ago be the cause of that?
_________________ My avatar shows the first encounter of Yuki in the Land of Eternal Snow. Yuki would become my favorite character in the on-going Mystics Saga by arrancar85
Well, you are linking to a post number that does not exist, so it is defaulted to the next higher post number, which is on Page 54.
The consequences of the splicing are ghost posts that cannot be viewed but they sometimes misalign the page count. They would have to be removed first to fix it.
_________________ Some people say, the universe is a Star Ocean!
Want to donate to keep the site up? PM me for possible donation ways!
We now also accept Bitcoin.
Sat: Well, you are linking to a post number that does not exist, so it is defaulted to the next higher post number, which is on Page 54.
edit: my mistake, see next page please
_________________ My avatar shows the first encounter of Yuki in the Land of Eternal Snow. Yuki would become my favorite character in the on-going Mystics Saga by arrancar85
Last edited by jacxxx on Fri Apr 13, 2012 11:04 pm; edited 1 time in total
You can post new threads in this forum You can reply to threads in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
Do not upload or mention any illegal content. Violators will be reported to the authorities. You are responsible for your uploads and actions.
If it is illegal for you to view adult lolikon material in your current location, leave this site immediately. LAH is in compliance with DMCA.
Month's top: Carnack with 100$
's mimicking the very small arrow 
Btw you can also check how the BBCode tags will behave from the preview button.
