FlatPress support forum

Hello,
I was saving a post & got an error mesage "corrupt index"
So I proceeded to rebuild index.
I now have what looks like a long list of Post [POST]Headings with entry numbers.
The top heading reads "BACKUP INDEX to fp-content/index1650371154"
I see a few index files @ the loction above...

The ...

Hello,
the code I received fro the Akismet site is not accepted as valid with the akismet pkugin... ?

Thanks Arvid !
It gives the posts a whole new look.

I would like to change the [Read More...] output to an 'image png'.
Any advice before I make the attempt ?

I think this is where the change should go...

line 71 - readmore.php
if (($q && $q->single) || isset($fp_params ['entry'])) {
$string = str_replace('[more]', "<a id=\"readmore-{$fp_params ...

Arvid wrote: The number of comments is hard-coded indeed. Check line 12 of fp-plugins/lastcomments/plugin.lastcomments.php - you can simply change that number to your needs.

Okay, I see it...thanks Arvid that helped

solution:
tried this and actually worked.
before 'Purge theme and templates cache', download lastcomments.tmp from [fp-content/cache/lastcomments.tmp].
...purge, then upload the lastcomments.tmp - thus retaining all the last comments from the widget.

Hello,
I had recently made a change with the blog. Based on what I have been used to with another blog software, I executed a purge to refresh things.
Right after the purge, I noticed the 'new comments' widget now reads 'no new commnts' on the main page. This surprised me since I had not expected ...

...and for last entries - direct view to page with comment window:

In 'plugin.lastentries.php'

$string .= "<a href=\"{$link}\">{$entry['subject']}</a>

replace with $string .= "<a href=\"{$link}comments\">{$entry['subject']}</a>


$string .= '<li>';
$admin = BLOG_BASEURL . "admin.php?p=entry ...

I was able to get the [more] to redirect to the page with comments.
by replacing #readmore-{$id} with 'comments' at both locations as shown below.
The 'comments' refer to the /comments prefix for the link.
Seems to be working tho - hopefully will not blow-up eventually.

This combined with Arvid's ...

found this in '/plugin.readmore.php