I was reinstalling a system to stage it live on the internet. The install kept failing, with the following error:

Code: Select all

 Parse error: syntax error, unexpected 'xxxx' (T_STRING) in /home/u848844205/public_html/winnifredbeach/mng/tags.php(2420) : eval()'d code on line 1

The 'xxxx' actually had a different value. I tried different names for the email before I realized that the password I was copying in ended with what is often an escape character, '\'. Once I changed the last character to something else, the install proceeded without issue.

If there are any problems duplicating this error, all the emails I had tried had the '_' in them, and the 'xxxx' part that was displayed in the error message contained the string that precededd this character.

This will probably be rarely hit, but I am quite confident it is a real bug, and not simply user error.

Thanks for a great script!

edit: I just remembered, I was also running under PHP 5.4. I made the mistake of changing to PHP 5.5 without being sure I retested the error, before changing the last character of the password. I am not sure, but I am guessing my hosting provider is using LightSpeed.

[KK]

Hi @atenhotep,

Thank you very much for reporting the matter.
I can confirm it is indeed a bug.

I've fixed it and will update the GIT repository soon.

Thanks again

I am glad, for once, I wasn't just moving too fast. Too many for me lately.

I wish I had more time to learn how your connecting to your DB layer. I get the
layout of the basic DB, but code connecting it maybe straight forward, but is long
enough that I haven't created the time to really try and digest it. I really would
love to see a lazyboycms based on couch and using flat files instead of a db
backend. Except for search functionality, I really think a lot of sites don't
need the complexity or overhead of a db, not for many SMB anyways. I am
sure there are satisfactory search solutions for a flat file based systems as well.

Anyways, thanks again for CouchCMS. It has made me not hate using a CMS
for web development. Most CMSs, are way more than I need, and/or way too hard to
make what should be simple changes with. Couch really hits the sweet spot and
does most of what you need out of the box easily while leaving HTML/CSS and
javascript as easy to work with as they are alone. I love it! You've made it fairly
straightforward to extend or even get what you need to out of the DB if you have
the background for that yet.

Really, and this may not be the place to ask, but how come there isn't a datetime
editable type? The extra work I had to do was only for that omission. If it was
simply cost/benefit in terms of a workaround, and most people's needs I get it.
However, it made more sense to me have a consistent contiguous Admin GUI
for event dates, than the example you provide in your tutorial on calendars. I know
for some of my users, even Couch's backend UI is going to seem a bit overwhelming.
[I haven't taken the time to implement the inline editing yet, and don't think in this
circumstance it was an option anyways. (Maybe via a data-bound form it was?
Hmmm, but then you're still overloading publish_date if someone wants to use it
for that.)]

Thanks again for a great piece of software!

[KK]

Thanks for those kind words, atenhotep

As for the 'lazyboycms' - you might be surprised to know that Couch began its life as a flat-file CMS. It remained so for several months during its development but then the inherent restrictions of not having a proper database started showing their effects.

I distinctly recall it was with a heavy heart indeed that I bid farewell to my flat-file version and ported everything to MySQL

Point is - I can totally understand your penchant towards a database free CMS. The thought of having a site in its entirety within a single folder has an alluring simplicity to it. But trust me, sites grow. A simple 5 page site today will soon demand something that will require a real database. And then you'll have to move everything to a more advanced CMS.

The decision to go with MySQL was to make Couch more future-proof.

but how come there isn't a datetime editable type?

Err.. did you miss seeing the following (or is it you meant something else)?
viewtopic.php?p=12667#p12667

[cheesypoof]

https://github.com/CouchCMS/CouchCMS/commit/1ee3dcaa44e11861638e60ce99f164e3d64bd495

Err.. did you miss seeing the following (or is it you meant something else)?
viewtopic.php?p=12667#p12667

Doh! Another moment.

I didn't search the forum for datetime, I admit. There is no reference to anything like
it in the docs online, and I just made it work anyways. I do know how to code, so sometimes
I just dig in.

Well, now I know there's the emotional energy to remember to search the forums right
after the documents, before working on something for myself.

FWIW, I noticed the documents download isn't as up to date as the website version either.
I actually spidered the website to have a more up to date copy of the docs locally.

Thanks again, can I say it too much?, for such an awesome tool!

Any chance of getting your old flat file code base? Even though it is not supported,
I'd happily compare it to what is out there. What I've noticed, when I've looked, is the
flat file "CMSs" being produced now are really mostly for developers for use for their
own sites. It is not hard for me, but I am not going to ask normal folks to learn
textile or markdown, as the "easy alternative" to HTML. They never want to see the
HTML, and they shouldn't have to. I am sure I am preaching to the choir here.

As for feature creep, especially, with a similar backend, I'd be happy to have businesses
pay me to migrate if they really need to, or do it themselves, because they know the
backend well enough. I can see wanting an RDBMS for even more complex blogging sites,
but I am talking about customers who you can give a blog, and you'll be lucky if you can
get them post something every two months.

At one level, what I am really looking for is a static site generator that has an easy GUI
backend for updating the site. Maybe that is the avenue I shoud do my next bit of
research on it from? I am loving CouchCMS enough though, that after getting someone
used to a backend, it would be awesome to have it be basically the same backend for
something more complex.

I can dream, and if I have time, I can do something about it. If you're willing I am curious
where you first hit those edges around wishing you had an RDBMS as you developed your
flat file Couch to an RDBMS Couch?