WordPress.org

Ready to get started?Download WordPress

Forums

Betta Boxes CMS
no. fields = 0 with wp 3.3 rc1 (14 posts)

  1. markus.zeeh
    Member
    Posted 2 years ago #

    If i add custom fields and click "save metaboxes" - no custom fiels will be safed. it shows 0. Mayby a bug wit 3.3. rc1?

    http://wordpress.org/extend/plugins/betta-boxes-cms/

  2. shauno
    Member
    Plugin Author

    Posted 2 years ago #

    Good spot Markus. I hadn't got around to testing the plugin with the latest WP yet.
    Seems the new version of jQuery included had removed a function I was using.

    Everything should be fixed now. Let me know how it goes once you've updated

  3. markus.zeeh
    Member
    Posted 2 years ago #

    Thanks for your work and bugfixing. But now i get a error 500 if i try to activate. Any idea?

    Thanks!

  4. shauno
    Member
    Plugin Author

    Posted 2 years ago #

    No idea why that would happen. I've just double checked a clean install of WP 3.3 RC1 and a downloaded copy of Betta Boxes and it activated fine.
    I will investigate and get back to you

  5. markus.zeeh
    Member
    Posted 2 years ago #

    Maybe it helps if you get a admin-account on my test-page? If yes, just send a mail to markus.zeeh(at)gmail.com and i will answer.

    Thanks! Markus :)

  6. shauno
    Member
    Plugin Author

    Posted 2 years ago #

    It seems that it most likely is a server issue. From what I can tell by a google search, is most people get this problem when they are running PHP4, or have too little memory.
    Are you hosing with 1and1 by chance?

  7. markus.zeeh
    Member
    Posted 2 years ago #

    Well, it looks like a realy strange problem: if i add your plugin (latest version) to my svn i get this error

    Warning: include_once(/Volumes/HD2/test.zeeh.no/viben/wp-content/plugins/betta-boxes-cms/types/.svn/.svn.php) [function.include-once]: failed to open stream: No such file or directory in /Volumes/HD2/test.zeeh.no/viben/wp-content/plugins/betta-boxes-cms/betta-boxes.php on line 85
    
    Warning: include_once() [function.include]: Failed opening '/Volumes/HD2/test.zeeh.no/viben/wp-content/plugins/betta-boxes-cms/types/.svn/.svn.php' for inclusion (include_path='.:/Applications/MAMP/bin/php/php5.2.17/lib/php') in /Volumes/HD2/test.zeeh.no/viben/wp-content/plugins/betta-boxes-cms/betta-boxes.php on line 85
    
    Fatal error: Class '.svn' not found in /Volumes/HD2/test.zeeh.no/viben/wp-content/plugins/betta-boxes-cms/betta-boxes.php on line 86

    It works fine bevor without svn. Any idea?

    Thanks for your time an work!
    Markus

  8. shauno
    Member
    Plugin Author

    Posted 2 years ago #

    The code on the line giving you an error is the code that is finding and including all the custom field 'types'. It assumes any directory inside the 'types' directory is a new type definition.
    When you added the plugin to your repository, SVN created it's own directories inside the types directory. The plugin is trying to include these directories as new custom field types.

    I have committed a fix to the development code. That should stop it trying to include svn folders.
    Download the 'Development Version' from http://wordpress.org/extend/plugins/betta-boxes-cms/download/ to test it.

    Is the plugin activating fine now?

  9. markus.zeeh
    Member
    Posted 2 years ago #

    Hei Shauno!

    Yes, it works! Thanks a lot :)

  10. shauno
    Member
    Plugin Author

    Posted 2 years ago #

    I will commit that to 1.0.2 then, but I won't push out a whole new version for it.
    Glad it's sorted for you. Hope you enjoy the plugin.

    [ Signature moderated. ]

  11. markus.zeeh
    Member
    Posted 2 years ago #

    Hi Shauno!

    Thanks and it works fine - but i found another bug. If i add a html-custom field the tinymce crashes on both places (content & custom field). Its testet with 3.3. rc3

  12. shauno
    Member
    Plugin Author

    Posted 2 years ago #

    I tried with RC1 and then the latest trunk (bleeding edge) and I couldn't get it to break. I don't feel like installing RC3 now :)

    What constitutes a crash?
    Do you have other custom fields?
    Is it on posts or pages?

    I appreciate the bug reports, they really help.

  13. markus.zeeh
    Member
    Posted 2 years ago #

    I just found the bug: if your use a custom lang (f.eks. norwegian) the tinymce doesnt work. If i switch back to eng. the tinymce works.

    Maybe it will be nice to use the new wp_editor() api?

  14. shauno
    Member
    Plugin Author

    Posted 2 years ago #

    I tried the wp_editor while developing the plugin, but it seems it was not built with the idea of having more than 1 editor per page. Perhaps it's improved since then, I will check it out when I get some time.
    I will look into localising the plugin. Sorry for the trouble right now :)

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic