Since upgrading from BigTree 4.0RC2 to 4.0.2, I noticed searching in-page for a module does not work as well.  The interface I'm referring to is when you click on 'Modules' in the main menu and then click and Module.  From that table, the search results quality seems reduced.  Here is some debugging info if it's helpful.

The query being generated is something like the this:

SELECT * FROM bigtree_module_view_cache WHERE view = '29' AND (column1 LIKE '%home%' OR column2 LIKE '%home%' OR column3 LIKE '%home%')This query is generating by converting all the search parts to lowercase but then does not return any results that contain the word 'Home' in uppercase, even though that is what the search query was.

Hope this helps, let me know if you need any more info.

-Michael

Hi, guys:

I thought I would throw out a suggestion that I think has the potential to revolutionize (pardon if this eventually seems exaggerating) BigTree and really make it stand out from other CMSes than I feel it already does.

With the possible caveat that rich text editors can give you a little more control (I, personally, don't think so but I am sure there are use cases), I think the best approach to content entry would be using the 'contenteditable' attribute.

If you're familiar with Medium.com, they use this to write their posts and I think it's becoming increasingly more common.  They also have a very lean framework of Javascript to control input.  I think it would be straightforward enough to create a lean framework around the entry of special structures into this content editable area (such as a callout like a photo gallery).  Moreover, it dramatically increases the flexibility and even paves the way for a truly drag-and-drop interface.  For more on what I'm talking about, see my previous post: http://www.bigtreecms.org/discussion/di … -templates and for a good example of a drag-and-drop CMS (although much else about it is bloated and poor, in my opinion, is Adobe CQ (formerly Day CQ) or now called Adobe WEM).

This method also lends itself to realtime saving of drafts.  I'm also imagining that the lean framework allows entry of a 'callout' on the page whereby filling in the fields for a piece of content, retrieves the generated markup and inserts it where desired.  The inserted content itself would not be editable as the 'rich text' is, but can present the same dialog box to constrain input when double-clicked or triggered in some other.  What's more, this avoids the awful overhead and load times of some rich text editors and frees you and your product from another dependency.

A quick list (some re-iteration) of how this would improve the user experience: potential in-page editing, flexible content entry, real-time saving of drafts, potential for a future drag-and-drop interface, reduced overhead, load times, and dependencies.  I don't believe I'm terribly oversimplifying at least given the scope I've outlined, although I'm still familiarizing myself with the API for this feature.  But I see a custom implementation centered around this feature being increasing a choice for many content-driven websites as it's intended to be included in the final HTML5 spec.  With the right foundation in place, I would love to help contribute to this kind of improvement to BigTree in the future.

-Michael

I was wondering if you have a recommended approach in mind for integrating an application into BigTree built with a framework. Specifically, this is the feature described as 'Plays Well With Others - Non-blocking/nestable sites allows other apps to live inside your site.' Some of the questions/issues I am encountering are:

The application should ideally run from a BigTree template so there is no duplication of the site's design, etc. Should the template be routed or basic? How can I best separate out the URI segments for BigTree from those for the PHP framework? What other configurations need to happen? Any important considerations concerning routing or other features of BigTree?  Any examples?

Happy to provide more specific questions as well.

Thanks,
Michael

I'm trying to install BigTree on my server with the following software and it's not working.  I am presented with a 404 page after seemingly successful installation of the example site.  Viewing the database shows that no pages exist in the pages table.  Manually importing the example_site.sql file does not work because it seems some entries were imported and redundancies cause a failure.  Installing without the example site and then manually importing example_site.sql does not work either.

Apache 2.4.4
PHP 5.4.12
MySQL 5.6.12

Any thoughts as to why this would happen or how to troubleshoot?

-Michael

I was wondering if you could perhaps expand a little more on the feature "Non-blocking/nestable sites allows other apps to live inside your site."

For example, what are the best practices, recommended approaches to nesting sites within BigTree? Specifically, we have a number of discrete applications we would like to keep separate from BigTree but be able to include them in the page.  Should we just use text fields and input PHP includes to call the scripts?  What should we be careful of when posting data, etc.? Since there is little documentation on this feature, it's difficult to form questions so apologies if this is vague.  Any help is appreciated.

Thanks,
Michael

Wanted to share the method I used to batch upload files.  There is a great plugin out there called Dropzone.  I included the CSS and Javascript in the admin panel and in my custom CSS, overwrote the BigTreeFileManager.addFile method.

This basically creates the dialog like the original function but with the content and some other parameters changed (final parameter for onCancel no longer applies) and stores the dialog in a variable.  The footer is in the form originally, so we remove the footer, apply the dropzone class to the form, append the footer to the dialog (for a close button which does not need to be in the form) and apply Dropzone to the form.

BigTreeFileManager.addFile = function() {
        var dialog = new BigTreeDialog("Upload File",'<input type="hidden" name="folder" value="' + this.currentFolder + '" />',false,"folder",false,"Upload File",true,this.finishedUpload);
        dialog.dialogWindow.find("form").addClass("dropzone").find("footer").remove();
        dialog.dialogWindow.append('<footer><a class="button bigtree_dialog_close">Close</a></footer>').find(".bigtree_dialog_close").click(function() { $(".bigtree_dialog_overlay").last().remove(); BigTreeFileManager.finishedUpload(); });
        var myDropzone = new Dropzone(".dropzone", { url: "admin_root/ajax/file-browser/upload/" });
        return false;
    };

It's a great library and I think worth considering for inclusion in the next release.