This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
211
Bug reports / Re: Confirmed issue list
« on February 27th, 2014, 10:26 PM »The database value you're trying to insert does not exist: id_file http://wedge.org/pub/bugs/8416/aeme-the-database-value-you-re-trying-to-insert-does-not-exist-id_file/
LiteSpeed + Pretty URLs = cannot reply http://wedge.org/pub/bugs/8435/changing-quick-reply-to-don-t-show-by-default-breaks-reply-new-topic-etc/msg293920/#msg293920
212
Off-topic / Re: Basic help with GitHub please
« on February 27th, 2014, 08:33 PM »
IMHO files edited directly are not signed-off?
213
Off-topic / Re: Basic help with GitHub please
« on February 27th, 2014, 08:05 PM »
I also had problems with TortoiseGit.
So I switched to SourceTree. Perhaps this is the right choice for you too.
http://www.sourcetreeapp.com/
So I switched to SourceTree. Perhaps this is the right choice for you too.
http://www.sourcetreeapp.com/
214
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 27th, 2014, 03:10 PM »
Go to: /do/admin/?area=manageboards;sa=board;boardid=1 (or whatever your boardid is).
There you can change PURL's settings for the desired board. Normally there is a select box where you can choose your URL (if defined).
There you can change PURL's settings for the desired board. Normally there is a select box where you can choose your URL (if defined).
215
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on February 27th, 2014, 02:56 PM »
Am I wrong?
You can change your URL in Admin->Boards?
You can change your URL in Admin->Boards?
216
Features / Re: Stuck on a programming model...
« on February 24th, 2014, 08:29 PM »
It's because MySQL's UTF-8 before 5.5 is "fake UTF-8"? It only supports 3 bytes per character max., so there is no way to directly store unicode characters plane in MySQL. :geek:
So we should lift up to 5.5?
This will bring the advantage of using "real UTF-8 support" (so you should not bother with serialize errors) and TEXT are also stored inline. :)
And from my personal point of view:
MySQL is almost at the level where InnoDB can perform fulltext search and MyISAM will be almost completely outdated and Wedge is the next generation forum software. So why .... ?
So we should lift up to 5.5?
This will bring the advantage of using "real UTF-8 support" (so you should not bother with serialize errors) and TEXT are also stored inline. :)
And from my personal point of view:
MySQL is almost at the level where InnoDB can perform fulltext search and MyISAM will be almost completely outdated and Wedge is the next generation forum software. So why .... ?
217
Features / Re: Stuck on a programming model...
« on February 24th, 2014, 07:50 PM »
VARCHAR is stored inline and is usually faster than text :)
218
Features / Re: Stuck on a programming model...
« on February 24th, 2014, 05:57 PM »
Yes, you are right.
Then it's better to use VARCHAR instead of BLOB.
And who cares about space in DB? It'll be cached anyway :)
Then it's better to use VARCHAR instead of BLOB.
And who cares about space in DB? It'll be cached anyway :)
219
Features / Re: Stuck on a programming model...
« on February 24th, 2014, 04:48 PM »
Forget about the first post.
Anyway. If you serialize data into MySQL it's better to do it the save way because MySQL is very picky when it comes to special chars and serialisation gets corrupted.
Use base64_encode and decode. And please make sure the field is a BLOB column.
Anyway. If you serialize data into MySQL it's better to do it the save way because MySQL is very picky when it comes to special chars and serialisation gets corrupted.
Use base64_encode and decode. And please make sure the field is a BLOB column.
220
Features / Re: Stuck on a programming model...
« on February 24th, 2014, 04:29 PM »Perhaps try to check if it is serialized and then if validated de-serialize it:
if( $unserialized = @unserialize( $row['data'] ) )221
Archived fixes / Re: Pretty URL | Unable to Post
« on February 21st, 2014, 04:28 PM »
So this would also affect profiles, gallery and so on.
Don't know if it's wise to remove support for it.
Perhaps leave it as "unsupported feature".
Don't know if it's wise to remove support for it.
Perhaps leave it as "unsupported feature".
222
Plugins / Re: Plugin idea - Mark as Sold
« on February 21st, 2014, 09:10 AM »I suppose it'd make even more sense to make a unified plugin with ability to choose what type of text is allowed, for what boards.
223
Plugins / Re: Plugin idea - Mark as Sold
« on February 21st, 2014, 09:05 AM »
Attached the working zip in previous post.
224
Plugins / Re: Plugin idea - Mark as Sold
« on February 21st, 2014, 08:59 AM »
Right,
don't know how this could happen. Will renew it today.
Anyway the working plugin is in my plugin repo on GitHub.
don't know how this could happen. Will renew it today.
Anyway the working plugin is in my plugin repo on GitHub.
225
Plugins / Re: Plugin idea - Mark as Sold
« on February 20th, 2014, 11:04 PM »
Hmm...
For people with classiefied boards, this plugin makes sense.
For people with classiefied boards, this plugin makes sense.