Wishes for future versions of CuteNews (Page 5 of 13)

I'm thinking of making autoarchive, that whenever an article is older than a specified date it gets automatically moved to the archive. Maybe someone made this already but w/e.
About auto-delete, I think that's something nobody would use anyway, if you think your archive or news.txt is too big, just once a year manually edit it and take the lost 200 lines away or something. If you want to see which date it is, put the first number into <?PHP echo date("D M Y","1110670102"); ?> and you'll see what date that line is. Remove the corresponding lines from comments.db.php.

cutehack automatically arranges them by date (in the case that the dates have been mixed up)

and yes oliver there is an auto archive hack but it doesnt work woth shit on 1.3.6 and cutehack

not so that they are in order of date, so that they are in any order you want them to be.

for example, i use cutenews as a next gigs list for my mate's band's website, so he (who knows nothing about web design) can just logon and add gigs to the list. i have it so that the oldest news is at the top, so that the earliest gig entry is at the top...

the problem is that when he gets a gig that is before their current last gig, that listing appears at the bottom and the list of gigs is not in order of when the gigs are. god that was difficult to explain. i hope it makes sense.

at the moment there are two solutions but neither of them are suitable for me:

A) use the alphabetical sort code - and then make sure the title of the news is the date of the gig. the problem with this is that i'm in the UK and i would have to use a date format that makes no sense in order for it to work - i.e 2004/03/15

B ) use the cutedateedit program which means you download the news.txt file and edit the times the news items were posted and then reupload the news.txt file. the problem with this is that my mate knows nothing about FTP, i don't want him to have my FTP password, its a lot of hassle and it generally defeats the point of using cutenews....

ok, so i could use some calendar program instead of cutenews, but it would be so much better if you could just go to edit news and then be able to drag and drop the order, or even just renumber the news articles....

this is the website im talking about http://www.thefishbrothers.co.uk/

right, this sounds promising - excuse my ignorance, but is cutehack an online thing?

do i install cutehack onto my webspace, replacing my existing cutenews folder - so that the band can logon as usual - but then have the ability to edit the post times etc?

the only reason i ask, is my main problem is i want my computer illiterate friends to be able to edit the post times online....

I'd like to see some simple logging, I use CN on a couple of community sites as pretty much a CMS, I have about 15 journolists and 2 editors on one site and I would like to have simple logging of who edits what.

I'm sorry to say I'm a bit confused about this forum because, for one thing, the users of CuteNews don't know when the next release will take place and, for the orther thing, there's a nasty dispute among some CN hackers. This situation is negative for everybody but specially for those like me who are waiting for new CN changes to update our hacks or addons. Will the next release be similar to CuteHack? Will it be the same as it is now but with some bug fixes? Will it have new options? These are some questions that hover above our heads and that need to land on safe ground. This is a very busy forum which needs a bit of order and clear things. But it is a good forum, so let's not spoil it.

An inclooded forum and a pool... all editable in the cutenews administration panel and activetable in the cutenews options... with editable templates.....
All that with out any mysql support...

Its a news management system here people, try and remember that

Check here: https://cutephp.com/forum/index.php?showtopic=6941

What like:

Cat 1
<?PHP
$category = "1";
include("etc...");
?>
Cat 2
<?PHP
$category = "2";
include("etc...");
?>

Hi guys!

I've not posted here in a LONG time, but some people will remember me for introducing plugins into CuteNews and more specifically: eruin's AJ-Fork.

I apologise if I'm repeating everyone else in the thread here - it's got pretty big and I'm not in the mood to read them all right now. I've also not sen the code for about a year, so I don't know what features have been done in that time. So here's my thoughts:

* Database storage. MySQL, PostgreSQL & SQLite. Passwords in files is not a problem - almost every single PHP script has a password stored in this way as a flat file somewhere (usually in a config file, with permissions set so that it cant be editted).
* Front-end code separated from the core code. I've not seen the most recent CN code, but last time I looked it was a disgusting mix switching in and out of HTML all the time. This should not occur.
* Friendly URLs. Every blog system should be able to do this, IDs should NOT be in the URL in this case - especially if a database is supported (records can be moved to another server where the ID may have changed).
* Plugin/API calls throughout the code. This is a major feature of WordPress, Drupal, and many other big PHP scripts. Plugins bring in more developers and extra functionality. I saw that someone mentioned that all functions should be built in (e.g. auto-archive) - plugins are used to stop the core code getting bloated with unused features.
* Valid XHTML & CSS admin interface and news output
* RSS feeds built in (without having to set up a new template etc etc)
* Internationalisation + localisation. Preferably in a database, file-based if neccessary.
* Multiple categories per news item.
* Subcategories

Some ideas:
* Full podcasting support, with RSS encapsulation, file upload, etc
* Multiple authors per news item
* Multiple news sites run from one script (without messing with categories)

That's all for now. I might check back tomorrow some time

Oh, two more.

It'd be neat to have an avatar or bullet that signifies something is "new" -- say it was posted in the last 7 days or something.

Also, it would be nice for the article author to receive email when a commented is added to a story.