I moved my site to a new host and frontend works as supposed. However logging to admin backend ends up with an error: "The URL https://raw.github.com/s9y/additional_plugins/master/package_sidebar_en.xml (IP 185.199.108.133) could not be opened. Maybe the Serendipity or SourceForge.net Server is...

Hello, I've these error messages in database logs: ERROR: column "e.timestamp" must appear in the GROUP BY clause or be used in an aggregate function STATEMENT: SELECT e.timestamp FROM s9y_entries e LEFT JOIN s9y_entrycat ec ON e.id = ec.entryid LEFT JOIN s9y_category c ON ec.categoryid = ...

garvinhicking wrote:Yeah, this issue has been reported a few times already...sadly nobody yet volunteered to rewrite the referrer tracking code

How much logic is there on the php side? Can't we achieve reasonable result with just changes in sql - something in the lines that I've proposed.

Hello, Loooking into s9y database logs shows quite a number of this kind of error statements: ERROR: duplicate key violates unique constraint "[prefix]referrers_pkey" STATEMENT: INSERT INTO [prefix]referrers (entry_id, day, count, scheme, host, port, path, query) VALUES (17, '2008-03-28', ...

garvinhicking wrote:I've just committed a patch that will omit the version number when expose_s9y is disabled.

Can you do the same for emails sent from s9y.

With expose_s9y set as false then mail header should be:
X-Mailer: Serendipity
but is now:
X-Mailer: Serendipity/1.3

I've just committed to SVN a patch so that $serendipity['languages'] can now be overriden from serendipity_config_local.inc.php (with a complete array). IMHO merging the arrays is not really required. Thought a while and there's interesting side-effect. This approach will probably used a lot for th...

garvinhicking wrote:I've just committed a patch that will omit the version number when expose_s9y is disabled.

Thanks. Also many security-conscious server-owners will be thankful

I've just committed to SVN a patch so that $serendipity['languages'] can now be overriden from serendipity_config_local.inc.php (with a complete array). Thanks. The amount of possible users is not so big and they probably will manage their language list also this way. IMHO merging the arrays is not...

Yes, that is true, because this is a place where every blog software does expose itself. We do not want to strip this. If you absolutely must, you can create your own feed template. No trouble in the promotion of the blogengine, but the issue is in version number. So <generator>Serendipity - 1.3 ht...

Currently $serendipity['languages'] array in serendipity_config.inc.php defines the list of translations to be offered. As the file is overwritten in every update, then that creates problems for those who have made a new translation, but are just testing it on their own site(s) and haven't relesed i...

There is and useful feature in serendipity_config.inc.php - through expose_s9y you can manage how explicitly Serendipity tells the world its version. This works pretty fine, except in feeds accessed though /feeds/... urls. Therein in <generator> tag the blogengine version is still shown even if expo...

Sadly varchar(255) ist the maximum for varchars on MySQL systems, so that would mean we'd have to write up a blob/text field for those fields, which would increase the size of each entry. And changing SQL keynames is always much work to do for sqlite, mysql and pgsql update files. That's OK, portab...

Hello, I had a look at errors on database logs and noticed this error: ERROR: value too long for type character varying(255) STATEMENT: INSERT INTO {PREFIX}visitors (sessID,day,time,ref,browser,ip) values ... Found out that perfecly legal urls from shots.snap.com (you know, the system of mouseover s...

Hello, S9Y and Freetag plugin and Postgresql (now respectively at 1.1.2 and 2.85 and 8.x) have been creating these errors for quite some time. ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list STATEMENT: SELECT DISTINCT e1.entryid, e2.title FROM {PREFIX}entrytags AS e1 LEFT...

Just in case other bloggers want to use this fix :) I looked for a way to fix "relation "{prefix}visitors_count" does not exist" errors showing up in my blog's postgresql log. Since the plugin didn't correctly create {prefix}visitors_count table then the easiest was to run (just ...