Next release?

No, there is no release date for the final version yet. If everything goes well, the next release after preview 4 will be the first release candidate.

The current preview 3 release is already close (feature wise) to the final version.

Next release?

Two more months have passed... Any word on some sort of final version of ContentTeller?

Next release?

Whatever you have to announce... I look forward to it.

Next release?

Great, a few more days so you can tell us that it'll be a few good months before test 2 may be done. I mean is it so hard to release what you've coded so far? We don't even have a feature list! No one's gonna hold it against you if it's not perfect, it's not supposed to if it's a test release! The only reason I can see for you not to release test 2 is because you haven't added anything since TR1 and obviously everyone would be unpleasantly surprised.

The current code base need some initial testing and clean ups before I can release it to the public. The main problem are that there are sometimes huge database/template changes between the builds. Any template or database change makes it difficult to upgrade.

And why not announce it now?

Because it is one of the bigger announcements.

Next release?

Great, a few more days so you can tell us that it'll be a few good months before test 2 may be done. I mean is it so hard to release what you've coded so far? We don't even have a feature list! No one's gonna hold it against you if it's not perfect, it's not supposed to if it's a test release! The only reason I can see for you not to release test 2 is because you haven't added anything since TR1 and obviously everyone would be unpleasantly surprised.
if you'd release what you've done so far you'd get all the bug reports you'd need, even about bugs you might have missed.
I think between running NTCompatible, LinuxCompatible, and now Techspot, plus handling all the clients who have bought your script, you've stretched yourself too thin.

I think the main reason why the new version is making slowly progress is that everyone expects a new version of an existing product that includes some new features. Contentteller isn’t a new version, but an entire new product.

So now it's our fault for expecting a new version?
And one that has some of the features that should have been in there in the first place?.
I have 15 000 thousand records in my downloads table and I can't edit them from the admin section because there is no way to page through a large number of records. I have to search in PHPMyadmin for the record I need to change and do it from there, because the admin section can only display the first 100 records. Was a rewrite from scratch needed for this?
And the same goes for the way they are displayed under category listing.

After looking over the situation I think I found the best way to exit this vicious circle. There is radical change coming, which I will announce, in the next few days. This change will result in a much faster development cycle next year.

Meaning the next version will have been more than four years in development because I understand it won't be ready this year.
And why not announce it now?

Another thing that makes the situation worse is that the new code base needs more testing but I am far to busy with the features

Well if you'd actually release what you're working on, we could do the testing. The "no time to work on it because I have to do testing" excuse doesn't really hold. Nor is the "I can't release 2.0 test 2 because you can't install it over test 1 which people are using in production". Somehow I doubt people use it in production environments considering it's encrypted, the templates aren't editable, and if anyone decided to actually edit them, they might have to be edited again since you said the templates in TR2 might not be compatible with the ones in TR1, and the only available feature (news) doesn't even work properly

Also, since we're talking RSS:
CT 20 has problems with quotes:
A title like
The Terminator Will "Be Back" From Dynamite Entertainment
which gets imported correctly in 1.8.2 is imported as
The Terminator Will "Be Back" From Dynamite Entertainment
in
Contentteller Pro 2.0.0 Test 1

When using "import directly to news" for a news source, the URLs don't get parsed correctly:
the [url ] - [/url] code doesn't get interpreted.

Next release?

Will we get another upgrade extension this year? I brought my license right before I expected the new code to surface and still haven't even installed it because v2 isn't out properly and the current test release doesn't support PROPER vBulletin integration (comments etc.).

Every existing customer will have access to the final commercial version of Contentteller as soon it is available.

So I paid the cash and got a product I couldn't use and have been waiting over a year . Everything feels stalled without something we can actually use, meanwhile technology and the competition is moving on. There always seems to be an "unexpected event" or something similar but while I could buy that for a year I no longer consider it an acceptable excuse.

I am also not pleased having this product still in development after every new month is a loss in time and money for me

I think the main reason why the new version is making slowly progress is that everyone expects a new version of an existing product that includes some new features. Contentteller isn’t a new version, but an entire new product.

As I posted a few times before, the entire code base is newly written from scratch. So I need to implement the feature set of the original Storyteller version beside new features, which is a nearly impossible task. Another thing that makes the situation worse is that the new code base needs more testing but I am far to busy with the features. The entire situation is a vicious circle.

After looking over the situation I think I found the best way to exit this vicious circle. There is radical change coming, which I will announce, in the next few days. This change will result in a much faster development cycle next year.

Next release?

Will we get another upgrade extension this year? I brought my license right before I expected the new code to surface and still haven't even installed it because v2 isn't out properly and the current test release doesn't support PROPER vBulletin integration (comments etc.).

So I paid the cash and got a product I couldn't use and have been waiting over a year . Everything feels stalled without something we can actually use, meanwhile technology and the competition is moving on. There always seems to be an "unexpected event" or something similar but while I could buy that for a year I no longer consider it an acceptable excuse.

I think everybody on here has been as patient as glass but now is the time to give us some fully functional code and commitment without further excuses. This isn't a FREE product so it shouldn't be treated like one, people have paid money.

Next release?

I will post this announcement early next week. Due to some unexpected events I had not the time to work on the project over the last 2 weeks.

Next release?

Originally posted by Philipp:

Actually, it had only a queue for PAD urls. Anyway, I started yesterday to extend the PAD queue to a full submission queue again. Should be finished later today

So, is it finished? I'm sorry if I sound a little bit rude, but if you can't meet a deadline, you shouldn't set it in the first place. It's very - let's say unprofessional - to say "it'll be ready in one or two months" over and over again, especially when it's been going on like that for at least 3 years now. It feels like a "well, at least that guy won't be asking when will it be ready for a month or two". attitude. You said you may release test 2 in September and it's almost December and there's no sign of it. Not even that update you said it you'd post "in a few days" when we talked by email two weeks ago.

Next release?

Any news about final realise day Philipp?

Next release?

Actually, it had only a queue for PAD urls. Anyway, I started yesterday to extend the PAD queue to a full submission queue again. Should be finished later today

Next release?

I wasn't comparing, I was telling it like it is now because I have yet to see 2.0 and how it improved the features 1.8 has. And I was asking if that problem was solved. It's nice to know that you took my PAD idea into consideration (I asked about it in an email conversation), but what about sofwares who don't use PAD? They should have a separate form to submit their softwares. But there is still a "waiting list" if you don't want to call it submission queue for downloads, right?

Next release?

The way it is now,..

You can’t compare the upcoming 2.0 release with the existing 1.x series. It is not just a new version but also an entirely new product. 99,99% of the code is newly written, I think there are only 4 subroutines from the original script left.

There should be something like keeping track who submitted what, so that a category of users such as "authors" could update the programs they submitted, but not those submitted by others. All you'd have to do is approve the changes they made. Does it have that?

There is no longer a submission queue, at least not in that way it was before. The new download module in now using a PAD database to track updates.

Next release?

Duplicate detection?

?
Possibility to update a program instead of adding a new one for each new version?

The way it is now, when someone goes to submit download and submits let's say opera 9.02, you'll get a new entry in the database instead of checking if a previous one exists. So opera 9.01 will be record 5010 in the table, and 9.02 will get added as a new record 6011 let's say.
This way if you want to keep the old download with its settings (subscribers) and statistics (download count for instance) you have to copy the changes from the submitted opera 9.02 manually over to 9.01.
It quicly becomes impractical if you get dozens of submissions.

There should be something like keeping track who submitted what, so that a category of users such as "authors" could update the programs they submitted, but not those submitted by others. All you'd have to do is approve the changes they made. Does it have that?

Next release?

For instance does the downloads module have features like "add to my downloads" for users?

No

Get notified by email when this program is updated?

Yes

Duplicate detection?

?

Possibility to update a program instead of adding a new one for each new version?

Already in 1.x

Related downloads?

Yes

Most popular programs in this category?

No

Newsletter that can be sent daily without admin input?
Meaning every 24 hours the CMS would send a newsletter with the downloads/news added that day?(Copying and pasting dozens of links into a newsletter is a definite time waster.)

No, but easily possible now.

Easily add multiple screenshots per program?

Yes

Fields like "whats new" for downloads instead of using extra fields for that? (take that as a suggestion, the downloads module could use some improvements, and extra fields are sometimes hard to manage).

Yes

Next release?

It's not like I'm asking you to write a novel.
But I have features that I need, which 1.0 doesn't have and I've been waiting for more than 2 years to find out whether 2.0 has them or not.

For instance does the downloads module have features like "add to my downloads" for users?
Get notified by email when this program is updated?
Duplicate detection?
Possibility to update a program instead of adding a new one for each new version?
Related downloads?
Most popular programs in this category?
Newsletter that can be sent daily without admin input?
Meaning every 24 hours the CMS would send a newsletter with the downloads/news added that day?(Copying and pasting dozens of links into a newsletter is a definite time waster.)
Easily add multiple screenshots per program?
Fields like "whats new" for downloads instead of using extra fields for that? (take that as a suggestion, the downloads module could use some improvements, and extra fields are sometimes hard to manage).
Yes or no for each will suffice.
Also, as a suggestion make the default size for extra fields larger. Often I'd had them truncated without any warning.

Next release?

The only problem is that I am currently fully busy finishing the Test 2 release. There is not much time left to write documentation or a feature list. I will publish such a list along with the Test 3 release.

Next release?

Well, that's a pretty vague answer. You sure you're not a politician? It would be nice if we at least had a list of new and improved features. I would assume that it is frozen by now, so it woulnd't be impossible for you to do that?

Next release?

Still doing code clean ups. This took much longer then I originally expected due of the size of the code base.

Next release?

So Philipp? How much longer? September is over, and no TR2.

Next release?

No, but I will post an update as soon the code clean up is complete.

Next release?

*wildly twiddles thumbs*

Is it done yet?

Next release?

Would this wipe out any customizations I make? How friendly do you believe the CT will be when upgrading (from final 2.0 to 2.1 for example).

It is much more upgrade friendly then the original 1.x series. Almost all modifications can be now with the templates or blocks.

One last question... how modular is CT?

The new version is very modular. You can easily plug in your own modules or remove existing modules without changing any line in the code base itself.

As you know I run a downloads section but I also have a drivers database that I most definitely love to port to CT, perhaps running two copies of the same module? How do you see that working from a developer's perspective? Or any other ideas on how to do it?

To run two copies of the same module, you need heavily change the duplicate module. Basically, you need to rename all functions as well the database tables of the module.

Next release?

You know the website I run, and besides that I'm desperately awaiting for integrating vBulletin with the news comments, I'm also in the process of developing a new website design/layout using CSS/XHTML.
I thought it would be much better if I could implement that straight on the new CMS rather than hopping over one to the other in a matter of a few months.

Only the forum module and a few other smaller things are not included in this release.

I don't use the forum module, which I guess is a positive thing if I want to jump in ahead of time.

I will test this release on a production website a few days before releasing it, but it might be better to wait until Test 3.

I definitely look forward the release and your test on the live site. I guess once you see it perform on such environment I will ask again if you recommend or not to install it.

You can upgrade from Test 2 to Test 3 by running the installer again

Would this wipe out any customizations I make? How friendly do you believe the CT will be when upgrading (from final 2.0 to 2.1 for example).

One last question... how modular is CT?
As you know I run a downloads section but I also have a drivers database that I most definitely love to port to CT, perhaps running two copies of the same module? How do you see that working from a developer's perspective? Or any other ideas on how to do it?

Thanks!

Next release?

With Test 2 coming out next month, what is the roadmap for CT towards the end of the year? How many RCs until final?

Right now it looks like that there will be only a Test 3 release a few days before the final version

How do you think Test 2 will differ from a final version?

Test 2 is almost code complete. Only the forum module and a few other smaller things are not included in this release.

Would you recommend its usage for production environments?

I will test this release on a production website a few days before releasing it, but it might be better to wait until Test 3.

If so, how will upgrading work from Test 2 to next releases?

You can upgrade from Test 2 to Test 3 by running the installer again

Next release?

With Test 2 coming out next month, what is the roadmap for CT towards the end of the year? How many RCs until final?

How do you think Test 2 will differ from a final version? Would you recommend its usage for production environments? If so, how will upgrading work from Test 2 to next releases?

Next release?

Well if you're still on schedule for September like you said above

No, Test 2 will be released in September instead of August.

One question: If I start working on the templates in 2.0 now, will upgrading to the next test release erase my changes? As in, do I have to wait for the gold release to edit the templates or can I do it now without worrying that the upgrade upload the original templates and overwrite my changes?

You can but I would wait until the Test 2 release. There are some bigger template changes between Test 1 and Test 2.

Next release?

Well if you're still on schedule for September like you said above (say you are please ),

you could expect a public release of Test 2 in August and the final release in September

Although I think I'd be happy with a functional news and downloads module, (news in TR1 has problems with quotes when importing news - I actually reported it some time ago,
and some encoded characters).

One question: If I start working on the templates in 2.0 now, will upgrading to the next test release erase my changes? As in, do I have to wait for the gold release to edit the templates or can I do it now without worrying that the upgrade upload the original templates and overwrite my changes?

Next release?

So, Philipp, when can we get a new test release?

I am currently cleaning up and adding some last minute features to Test 2. The new test release should be ready next month.

I'm worried that test release 1 is set to expire in December. Does this mean you don't expect it to be ready before next year?

I changed it because I noticed that some sites are using Test 1 in production environments. The higher expire date make it easier for such sites because there is less pressure to upgrade.

Next release?

So, Philipp, when can we get a new test release?
2.0 better blow us away, because I think it's been more than two years in the making.
Some time ago you said something about it being ready in fall. I'm worried that test release 1 is set to expire in December. Does this mean you don't expect it to be ready before next year?

Next release?

Everything delayed for another week but now I am back to development

Next release?

What site is that?
As you can see I'm eagerly waiting for the next CMS as well

Julio
 http://www.techspot.com

Next release?

There is again a slight delay due an unexpected event. I acquired along with a friend a tech news website and working right now to get the site up and running. I am fully back to development as soon the site is re-launched (mid next week).

Next release?

How's the release coming along, Philipp? Things looking to be on schedule?

Next release?

Do you mean the templates? Yes, there is no way to import the old template set to the new version. All other things including the news and content can be import with an import tool.

Next release?

Did you mention that Contentteller 2 will not be backwards compatible with 1.0, so a person would have to manually edit all the files in 2.0 if they started using the 1.x version, right?

If so, I will patiently wait for the 2.0 release.

Next release?

Yes and no.

I originally planned to release every 4-8 weeks a new test release. However, I changed this plan after there was less feedback on the first Test release. Another problem of the previous test schedule was that none of the test releases were able to replace older 1.x installation due to the limited feature set.

Test 2 will be released as an almost feature complete test release. All modules are included in this release. Looking at the current development speed I would say that you could expect a public release of Test 2 in August and the final release in September. There will be also a Test 3 release, which will be released a few days before the final version to catch some last minutes bugs/problems.

Additionally, I will release next week a refresh of Test 1 with some minor fixes and extended expire date.