FORUMS CLOSED DUE TO SPAM. YOU STILL CAN ADD POST!

Forums → User →

Martijn (mvdkleijn) posts

Feed 651 posts

Is Frog and Wolf CMS by the same person?

I just have to respond to this one…

The correct answer to toya’s question is: No.

Wolf CMS was created by me as a fork of Frog after Philippe Archambault did not respond to requests, questions and generally was not present for Frog development. For full details see: http://forum.madebyfrog.com/topic/1437

In the mean time, I’ve been continuing development in Wolf CMS and its may look similar but a lot of stuff was added/fixed in Wolf. We now also have a four man project team.

If you are wondering why Frog CMS development suddenly stopped after I forked. Basically because I developed the last two versions of Frog and Philippe was not involved any more by his own(!) choice.

Want proof? Just check out the SVN repository listing: http://code.google.com/p/madebyfrogs/source/list

If you want the full list of changes that were made in Wolf CMS as opposed to Frog 0.9.5, please see this list: http://code.google.com/p/wolfcms/source/browse/trunk/docs/changelog.txt
(start reading from the bottom)
 

Forking Frog

I just wanted to reply to M’s fairly long post about the fork. Frog has largely been, in effect, a “one man development” from the very start. At first Philippe himself worked on Frog and versions 0.9.4 and 0.9.5 were mostly my doing.

While I agree there should be a core development team, which is why I’ve always spoken about “the team” and “the Frog core”, it is my personal experience which leads me to believe there should generally be an overall architect/project lead/lead developer who has the final say-so. At least in smaller projects.

I’ve been a developer myself for quite some time and have contributed to multiple open source projects. How you run a project depends very much on the project’s goals, size and how big you want it to be.

The new Wolf CMS project I have begun is intended for me. That might sound strange, egotistical or whatever but that’s the heart of it. The idea was to protect my so far considerable investment in the code’s future.

Having said that, it was always my intention to keep the code and its future available for anyone to use. I could have simply walked away from the project and continued development in private. Instead I have opted to share it and my time as an Open Source project.

I agree that any project should have clearly defined roles and that is exactly my intention with Wolf CMS. Though it will most likely never be a big team, it is not my intention to “go it alone” for ever. My idea is to set a general direction, get the project going, recruit non-developer team members and then slowly build up a reliable team of 3-5 core developers with commit access. Besides the core development team, I hope to have an active user community who is willing to send in patches and bug fixes.

Time is patient. ;-)

As for plugin compatibility: you will be happy to know that version 0.5.0 of Wolf CMS is a one-on-one copy of Frog 0.9.5. Since I have guided Frog’s plugin related features in both 0.9.4 and 0.9.5, that trend of development will continue with Wolf CMS.

While I won’t guarantee plugin compatibility between Wolf CMS 1.0 for example and Frog 0.9.5, at least in the near future, Frog plugins will happily run on Wolf CMS.

As for the discussion you propose, that train has left the station. I would never have forked if I thought it preventable and discussions/exchanges of thought have taken place.

While I appreciate that the users of Frog might want to have a say in all of this, my time is donated time. No disrespect intended here, but the users of Frog have absolutely nothing to say about how and where I spend my time. ;-)

Anyway, what I’m trying to say is: I’m not changing my mind about the fork, I’m too far in. Give it some time and see how I structure the new project before deciding whether it will live or not. Keep an eye out on the wolf cms website.

@easylancer – I think the Frog project has in effect ground to a halt. Sorry. I also think git is not the way to go. Again sorry. Creating patches against specific versions of a piece of software is not difficult at all and many developers have been doing so for quite some time. I have seen too many projects go down in flames due to too many developers with commit access “scratching their own itch”. :-)
 

Forking Frog

Yes, you are reading this correctly. I’ve decided to fork the Frog CMS project. It is with some regret that I do this since I’m personally not fond of people forking projects.

You can read the full announcement and reasons. In part, the reason for me forking the project is because of differences in opinion about the direction in which Frog should develop.

I wish Philippe all the best with the Frog CMS project in the near and distant future, but for me the road ends here.
 

Registered Users plugin ALPHA now available

To protect the admin area from exposure, edit yoursite.com/frog/app/main.php line 235 to read:

This should not be required with Frog 0.9.5. final. The first line in backend.php specifies that you can only access the admin area if you are either:

  • administrator
  • developer
  • editor

If you’re anything else or none of the above, you’ll get redirected to the front page.

Otherwise: nice going with the plugin. :-) Haven’t had time to look it over yet but sounds great!
 

[Solved] PluginController 'incude_once'

I’ll implement the change since its not a real big thing and generally makes Frog more robust.. but as a programmer I must say you seem to be doing a whole number of things just to prevent yourself from having to write the plugin id twice… doesn’t make sense to me.
 

Off to Japan

Hi all,

Since both Frog 0.9.4. and 0.9.5. have been mainly my efforts on the Frog core code, apart from a number of patches, I thought I’d give people here a heads-up.

If all goes well, I’m leaving for Japan this Sunday with my girlfriend. We should be there for about a month, so don’t expect much activity from me. ;-)

Anyone capable of reading Dutch is of course welcome to “track” me through my posts on my site however (in)frequent they might be. Anyway, I’ll of course be back after the trip.

Sincerely, Martijn

On another note –

Anyone that’s interested might like to know that someone created an Ohloh page for Frog. I thought I’d “manage” the Ohloh page, though that doesn’t amount for much. :-p Anyway, here it is: https://www.ohloh.net/p/frogcms
 

Q. Explain. How working a translation mechanism?

Read this: http://code.google.com/p/madebyfrogs/wiki/TranslatorNotes

And also check out the skeleton plugin which is supplied with Frog core and is intended to serve as an example of how to create a plugin.
 

TinyMCE plugin release 2.0.0 RC1

@davidhund – true.. I haven’t updated the TinyMCE plugin yet after I release Frog 0.9.5. I’ll see about updating it this weekend.
 

[Solved] PluginController 'incude_once'

I understand where the problem is coming from…. I must say I didn’t expect anyone to try and write their own plugin controller instead of just using the normal method to initialize the plugin. I also don’t entirely understand why you would want to?

That just makes it needlessly complex?

What you want to do in the controller doesn’t belong there in my opinion… it belongs in the index.php file. That’s how it was designed and there is a reason.

You could have multiple controllers in a single plugin for example. That would become rather difficult in your scenario.
 

RSS Parser?

Don’t know. Since BDesign’s site went down, I tried “rescuing” his plugins and I did manage to get some of them but not all. (like feedburner)

I’m willing to help debug the simplepie plugin, but tomorrow is the queens birthday bash which I was planning to attend so I’ll probably won’t be able to help out until friday afternoon or so. (unless the weather’s nice, then I’ll be out and about to get some air ;-) )
 

tinymce image list non existant

  • What are the values you entered on the settings page for the plugin?
  • What directory do your images live in?
  • If you used tinymce before… have you tried clearing your browser cache? (its javascripts after all)
 

Observers

My thoughts for the future direction of the security system in Frog where actually more going towards a combination of roles and permissions.

The current “administrator” and “developer” roles would be changed to be containers for certain permissions.

You could then setup permissions on certain types of actions/objects. For example, a certain role could have a “view” permission on pages but no “modify” permission.

I was thinking about something like: “View”, “Create”, “Modify”, “Administer”

Still just a brainstorm though, haven’t really given it much concrete thought yet.

The underlying principle would be to keep it as simple as possible, have a good clean default and it should allow you to say things like “Users with role XYZ are allowed to create objects of type Page”.

Notice the work objects… If we’d use something like this, I’d like to use the same set of permissions for everything in Frog. Pages, Comments, Layouts, Snippets, etc.
 

Frog version 0.9.5 stable released

This is a superb step forward. Martijn deserves a huge vote of thanks, IMO!

Aw gosh… (_)

I see he even tidied up his personal site for the occasion. ;)

Ah! You noticed that did you? :-p I thought this would be a better look.. still not finished with it though. And I’m going to do some rewriting on the download plugin. I’m currently using Bebliuc’s, but I’m not entirely satisfied with it. And he seems rather absent lately. :-S

Nice work all round, Martijn!!

Thanks. :-)
 

[Solved] PluginController 'incude_once'

What exactly is your problem? Can you describe it please? Then I’d have an idea why you want the change, not that I’m opposed to the change by the way.
 

Plugin security issue

I was already thinking along the same lines and added a cautionary INSTALL_SEQUENCE constant to Frog’s schema files in 0.9.5.

The idea tuupola had is sound… ALL php files belonging to Frog should have some sort of if defined in there unless they are specifically intended to be callable outside of Frog.

I’d suggest adding:

if (!defined('IN_FROG'))

and adding this to index.php

define('IN_FROG', true);

At least, that was the direction I was thinking of.
 

tinymce not working correctly

This warning shouldn’t impact the functioning of the plugin. You may want to replace line 42 by the following though:

$stmt->execute();

Other than that, no clear problems…

  • Does the tinymce table exist in your Frog DB?
  • What are the values in there?
  • What values (if any) are shown on the TinyMCE tab in the backend?
 

Frog version 0.9.5 stable released

Hi all,

I’ve just uploaded the release of Frog 0.9.5 to the madebyfrog.com site and Google code. Please see the related blog post.
 

TinyMCE (with frog in subdir)

Don’t think so since the TinyMCE plugin doesn’t belong to Frog core. Also, the readme included with the plugin states what to do. And the 1.3 plugin will soon be superseded by the 2.0 final plugin.
 

1&1 hosting - Get File Contents Error

In config.php:

define('CHECK_UPDATES', true);

Change to false. Note: this is for Frog 0.9.5
 

Frog Demo of templates broken

Hmmm… David is having some problems with his site. I’ve informed him of the problem.
 

Will the existing themes work with 0.9.5 ?

In general, existing themes should be compatible with 0.9.5. though it does depend heavily on how the theme was setup by the author.

The one thing that comes to mind which may be a small problem is that a default installation of Frog in 0.9.5 no longer has the stylesheets directory and such. This can offcourse be manually changed by altering the theme or by adding the missing directories.

The reasoning for changing the default content of the public directory was to provide some more structure for theme developers to encourage a standard approach to creating themes/layouts.
 

tinymce not working correctly

Can i upgrade without messing up the current site?

Assuming you know what you’re doing and you follow the upgrade instructions? ;-) Sure. But wait a couple of hours. I should have Frog 0.9.5. final pushed out the door before the end of today. (CET time)

when i go to the tinymce tab, and put in the paths to my CSS file, etc. And save, it says “settings saved”, but it does not keep the files i put in. Could this be a permissions issue?

Ah! That would be the real problem then. The TinyMCE plugin saves its settings in the database, so that shouldn’t be a problem.

  • What DB and DB version are you using?
  • Have you tried setting DEBUG to true in config.php to see if that yields more information?
 

TinyMCE (with frog in subdir)

I don’t know why TinyMCE is in the title name of this post, because the question is very generic.

Anyway apart from plugin specific settings, all plugins should generally work out of the box no matter in what directory you install Frog. In fact, my test environment is alway located in a subdirectory.

If this is about the TinyMCE plugin, look around on the forum. A lot of questions have already been answered.

For example, see:

http://forum.madebyfrog.com/post/6240/#post_6240
 

Test site not working !

324 is not an HTTP error code, so it sound like a problem on the host machine.. (all 3xx error codes are redirects, this isn’t) I’d suggest to investigate the machine itself. But I could be spouting nonsense. ;-)
 

tinymce not working correctly

That means tinymce’s javascript is not being loaded by the browser.

I don’t suppose you are able to use Frog 0.9.5 RC2 and the tinymce plugin 2? That would probably save you a lot of hassle in getting it up-and-running.