Jump to content
justb3a

Simple Contact Form

Recommended Posts

Good day! This module is so promising, but I just cannot manage to install it. I upload it like other modules with classname, install with no error massages. Then inlude the

$modules->get('SimpleContactForm')->render();

code in my contacts template and get the "Error: Exception: No Template was found." error as an administrator. The template was not created. I did set site/templates to 777 (tried it on local Windows and on remote Linux server). What am I doing wrong? Are there supposed to be errors when the template cannot be created?

Share this post


Link to post
Share on other sites

Confirmed, but I see that when I save the module settings, it says it can't create the templates. If I refresh from that error, the files get created... and then it all just works.

  • Like 1

Share this post


Link to post
Share on other sites

I'm really sorry, but I can't get it to work. I'm new at processwire, so maybe I did something wrong. I tried to follow all instructions and what I get and see on my contact page is an embedded form, with an unstyled list  of input files (which is ok, styling will not be the problem).

If I click the (empty or filled out) form, the front page of my processwire is loading. And that's it. No mail sent, no error or success message. 

Possibly there is an error in my template. The only difference I made is – instead of

$content = $modules->get('SimpleContactForm')->render();

I had to change to 

echo $modules->get('SimpleContactForm')->render();

In my contact template.

Maybe this causes the error?

Maybe someone can help? 

Thank you very much!

  • Like 1

Share this post


Link to post
Share on other sites

@Matzze: You installed the module the right way and everything works as expected. This module provides some spam protection methods - and if this fails you will be redirected to the root page (I should add this to the readme!). Have a look at site ▸ assets ▸ logs ▸ simplecontactform-spam-log.txt. I guess there is an error like "2015-03-30 13:38:50 Date difference is out of range." The reason is antiSpamTimeMin (It parses the time the user needs to fill out the form. If the time is below a minimum time, the submission is treated as Spam.) in module settings.

The html list is unstyled, you could/should change the html structure to your own needs as well as adding custom css.

@Mike Anthony, @Ivan Gretsky : I know this is not the best solution, if somebody has an idea to improve this, just let me know! It's really important to enter and save the module settings first because depending on this the template(s) will be created.

  • Like 2

Share this post


Link to post
Share on other sites

@justb3a: I am still a little confised about the connection between the inputfields in thr template and in the config. I do not know why but I thought that I can simply add fields in the config (separated by commas) and the will get rendered in the template. But it does not work this way in my case. Could you please explain that a bit.

Share this post


Link to post
Share on other sites

New version 0.1.1 - improved template handling as well as adding optional clear up functionality for uninstalling the module.


  • creating/updating templates after submitting the module settings
  • add and/or remove fields works but you have to check the html structure manually
  • additional checkbox for uninstall: "If you check the following box all data containing files as well as database content will be permanently erased with no chance for recovery. It's recommended to make a backup before uninstalling this module."

@Ivan Gretsky: Now you can add/remove fields in the config (separated by comma). But make sure to check your html structure because I do not know your html structure. It's not that easy to determine the position to insert/remove code.


  • Like 2

Share this post


Link to post
Share on other sites

hi,

i'm getting a sytax error ( Parse Error: syntax error, unexpected '[' (line 1151... ) in the SimpleContactForm.module after installation.

When i change line 1151 into ...end($split),1, 0... there is another error occurring ( Call to undefined function boolval() (line 316... )

after commenting that line out, the module works

PW 2.5.24

php 5.3.29

can you reproduce that?

Share this post


Link to post
Share on other sites

@Christophe: Thanks now the links should work. The processwire module directory imports the readme from github. The problem is that I have to use absolute links in my github readme to make them work there. Relative links get the process wire module directory prepended (for example [installation](doc/installation.md)leads to modules.processwire.com/modules/simple-contact-form/doc/installation.md which does not exist). It's a bit annoying because an absolute link includes the name of the current branch which has to be master. And so I'm not able to test it before making a new release. The same applies for images.

Share this post


Link to post
Share on other sites

@justb3a

had some issues; spent about 2 hrs trying to get this to work; some of the documentation does need improvement, for example it should say to echo the module, or the module should echo.

for one, there should be a way to disable the whole spam thing, besides putting in the ip address.

makes it hard to test;

sometimes i'm trying to test this and it's redirecting to the homepage, sometimes the form just shows again with the fields filled in, i have no idea what is wrong; and then i'm trying to do a simple form and change the markup but it either seems to break, or it triggers the spam thing.

the message area should be a textarea; seems that changing from input to textarea also was messing things up;

i appreciate all of the hard work that went into this, just seems that it could use some additional improvements and some better documentation..

for now i'll have to stick with formbuilder for this site, but have somee friends who need to use this; so we'll have to sort out this textarea thing, and also how to completely disable the spam thing. plus i can fill out a form in way less than 1 minute, so how can that be a real spam prevention technique; doesn't make so much sense; maybe consider some simpler spam prevention like honeypot...

thanks for listening.

  • Like 1

Share this post


Link to post
Share on other sites

had some issues; spent about 2 hrs trying to get this to work; some of the documentation does need improvement, for example it should say to echo the module, or the module should echo.

It should be clear that the module should echo, I removed the echo keyword from my documentation because if you download for example ProcessWire, it contains some basic templates and you will need $content = $modules->get('SimpleContactForm')->render(); to output the form. So if you use a template prepend file or if you use for example TemplateDataProviders it differs.

for one, there should be a way to disable the whole spam thing, besides putting in the ip address.

I think about that, for now just enter antiSpamTimeMin = 0 (Maybe I should set this as default?), antiSpamTimeMax = 1000 and antiSpamPerDay=1000.

makes it hard to test;

sometimes i'm trying to test this and it's redirecting to the homepage, sometimes the form just shows again with the fields filled in, i have no idea what is wrong; and then i'm trying to do a simple form and change the markup but it either seems to break, or it triggers the spam thing.

This modules creates two log files (→ documentation), have a look there to figure out what is wrong. If you were redirected to the homepage (→ documentation) the reason is always spam protection. If you change the markup make sure to maintain the names of the fields and you have to hide website(honeypot field) and submitted (→ documentation). If you change the number of inputs manually (adding or deleting a field), you have to adapt antiSpamCountAdditionalInputs (→ documentation).

the message area should be a textarea; seems that changing from input to textarea also was messing things up;

You enter the fields as a comma separated list, maybe there will be more textarea fields like `message`. How should I know which one should be a textarea and which one a simple input or maybe a date input (for example). This module provides some templates as starting point, you have to change / adapt the html! The honeypot field is also displayed because it's better to add a surrounding div assigning a class and hide it using CSS. 

i appreciate all of the hard work that went into this, just seems that it could use some additional improvements and some better documentation..

Feel free to contribute! You could at least help me to improve the documentation!

for now i'll have to stick with formbuilder for this site, but have somee friends who need to use this; so we'll have to sort out this textarea thing, and also how to completely disable the spam thing. plus i can fill out a form in way less than 1 minute, so how can that be a real spam prevention technique; doesn't make so much sense; maybe consider some simpler spam prevention like honeypot...

Nobody has to use this module! Go ahead and use formbuilder. You can fill out the form in less than one minute, just set timeMin = 0! It's the same as disabling spam protection. There is much more spam protection and of course there is already a honeypot field.

  • Like 3

Share this post


Link to post
Share on other sites

ok thanks for all your help and info- i will try it again, i didn't know anything about honeypot and that the website field was the honeypot must have somehow missed that in the docs.

so can i just change the message input to a textarea, and it should work i guess. i will test and post back results.

Share this post


Link to post
Share on other sites

Hi there. This is a really nice script, and it works really fine! Is there a possibility to use it more than once in my project? I nee a simple contact form and more customized one for other requests. Can i "duplicate" the full script it maybe?

Thanks for helping!

Share this post


Link to post
Share on other sites

At the moment there is no way to use it more than once in a project. I guess duplicating is not that easy because you have to adapt all template and field names as well.

Share this post


Link to post
Share on other sites

I only can send an input type textarea with a maximum length of 255 chars. In your module you use sanitizer->text. Per default every Text of any inputfield will be truncated at 255 chars. It would nice if i can send 16384 chars in this type of input field (textarea). Is there any solution to fix this? Thanks.

So - kind a quick&dirty - but that solves my problem first.

Line 433 of SimpleContactForm.module

 if($inputfield == "Nachricht"){
        $message[] = $inputfield . ': ' . $this->sanitizer->textarea($this->input->post->{$inputfield});
      }else{
        $message[] = $inputfield . ': ' . $this->sanitizer->text($this->input->post->{$inputfield});
      }

& Line 481

 if($inputfield == "Nachricht"){
              $newEntry->{'scf_' . $inputfield} = $this->sanitizer->textarea($this->input->post->{$inputfield});
            }else{
              $newEntry->{'scf_' . $inputfield} = $this->sanitizer->text($this->input->post->{$inputfield});
            }

Anyway - mayby you could consider this in one of the following versions.

Share this post


Link to post
Share on other sites

Do you use the latest version? I know this issue and fixed it already some weeks ago. Have a look at github. The only occurence of $this->sanitizer->text is on line 417 in the function validateFields. Maybe I should change this as well to textarea.

Share this post


Link to post
Share on other sites

Hello,

i'm new to processwire, but i really like it. This add on is a great enhancement.

How can i change the text in a submitted e-mail? Example

fullName in Absender

thanks

Share this post


Link to post
Share on other sites

Hi Congomonster,

you have to change the fieldname. in your case scf_fullName in e.g. scf_Nachname. Be carefull. the prefix scf_ is important.
And you also have to change the values ( input - Tag ) in your form. But here you go without the prefix!
Don´t forget to adapt the fieldnames in your modulconfiguration. also without the prefix.
 

  • Like 2

Share this post


Link to post
Share on other sites

hi justb3a,

ok, i will figure this out - Thanks a bunch!

Anonther issue appears shortly:

when i try to call the page scf-messages, a run "max execution time" - error appears.
do you have an idea, how to fix that or what this error causes?

Thanx!
 

post-2037-0-36408200-1434514820_thumb.pn

Share this post


Link to post
Share on other sites

@itsberni: Have a look into you php.ini file. There is an entry for max_execution_time. Check that value und increase it. And also have a look at max_input_time and memory_limit.

@congomonster: Maybe I should provide a way to write your own email content using placeholders. Then you would be able to add additional text as well. 

Edit: I opened an issue regarding that feature on github, so I keep it in mind  ;)

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      First a note about my other modules...
      I have three existing modules that are similar in that they allow restrictions to be placed on repeating inputfields: Limit Repeater, Limit PageTable, Limit Table
      Restrict Repeater Matrix takes a different approach to the module configuration from those other modules. The module settings for Restrict Repeater Matrix are applied in the field settings rather in a module config screen. I think this new approach is better, but it means that it isn't practical to create different settings for different roles via the admin interface. Instead the module has a hookable method, allowing roles to be targeted and other advanced usages to be achieved via a hook. The result is that the module is more flexible.
      I intend to transition my other modules to the same approach over the coming weeks, but because this will result in breaking changes I will be releasing the updated modules under new names ("Restrict Repeater", etc) to avoid users upgrading via the Upgrades module without full awareness of the changes. The old modules will be marked as deprecated.
      Restrict Repeater Matrix
      A module for ProcessWire CMS/CMF. Allows restrictions and limits to be placed on Repeater Matrix fields. Requires ProcessWire >= v3.0.0 and FieldtypeRepeaterMatrix >= v0.0.5.
      For any matrix type in a Repeater Matrix field you have the option to:
      Disable settings for items (cannot change matrix type) Prevent drag-sorting of items Prevent cloning of items Prevent toggling of the published state of items Prevent trashing of items Limit the number of items that may be added to the inputfield. When the limit is reached the "Add new" button for the matrix type will be removed and the matrix type will not be available for selection in the "Type" dropdown of other matrix items. Please note that restrictions and limits are applied with CSS/JS so should not be considered tamper-proof.
      Usage
      Install the Restrict Repeater Matrix module.
      For each matrix type created in the Repeater Matrix field settings, a "Restrictions" fieldset is added at the bottom of the matrix type settings:

      For newly added matrix types, the settings must be saved first in order for the Restrictions fieldset to appear. Set restrictions for each matrix type as needed. A limit of zero means that no items of that matrix type may be added to the inputfield.
      Setting restrictions via a hook
      Besides setting restrictions in the field settings, you can also apply or modify restrictions by hookingRestrictRepeaterMatrix::checkRestrictions. This allows for more focused restrictions, for example, applying restrictions depending on the template of the page being edited or depending on the role of the user.
      The checkRestrictions() method receives the following arguments:
      $field This Repeater Matrix field $inputfield This Repeater Matrix inputfield $matrix_types An array of matrix types for this field. Each key is the matrix type name and the value is the matrix type integer. $page The page that is open in ProcessPageEdit The method returns a multi-dimensional array of matrix types and restrictions for each of those types. An example of a returned array:

      Example hooks
      Prevent the matrix type "images_block" from being added to "my_matrix_field" in a page with the "basic-page" template:
      $wire->addHookAfter('RestrictRepeaterMatrix::checkRestrictions', function(HookEvent $event) { $field = $event->arguments('field'); $page = $event->arguments('page'); $type_restrictions = $event->return; if($field->name === 'my_matrix_field' && $page->template->name === 'basic-page') { $type_restrictions['images_block']['limit'] = 0; } $event->return = $type_restrictions; }); Prevent non-superusers from trashing any Repeater Matrix items in "my_matrix_field":
      $wire->addHookAfter('RestrictRepeaterMatrix::checkRestrictions', function(HookEvent $event) { $field = $event->arguments('field'); $type_restrictions = $event->return; if($field->name === 'my_matrix_field' && !$this->user->isSuperuser()) { foreach($type_restrictions as $key => $value) { $type_restrictions[$key]['notrash'] = true; } } $event->return = $type_restrictions; }); http://modules.processwire.com/modules/restrict-repeater-matrix/
      https://github.com/Toutouwai/RestrictRepeaterMatrix
    • By BitPoet
      Here's a little text formatter module that redirects all external links found in a textarea (e.g. for hit counting) to a given URL.
      TextformatterExternalRedirect
      GitHub repo
      As TextFormatters do, this module modifies the contents of the textarea (HTML) at rendering time. It prepends the given URL to the link address for external links (http and https), optionally makes sure that the link is opened in a new window and allows you to add css classes to such links.
      All options can be configured in the module's configuration settings.
      Usage:
      Download the zip archive and extract it to site/modules, the rename the top folder to TextformatterExternalRedirect Go to the backend and select "Modules" -> "Refresh", then click "Install" for "External Link Redirect" Click "Settings" and configure the module
      Go into the field configuration for the field(s) you want this formatter to apply to and add it from the dropdown
      Done, now any external links in the configured fields will have the configured settings applied Feel free to leave feedback and post and questions you have here.
       
    • By teppo
      Hey folks!
      Took a couple of late nights, but managed to turn this old gist of mine into a proper module. The name is SearchEngine, and currently it provides support for indexing page contents (into a hidden textarea field created automatically), and also includes a helper feature ("Finder") for querying said contents. No fancy features like stemming here yet, but something along those lines might be added later if it seems useful (and if I find a decent implementation to integrate).
      Though the API and selector engine make it really easy to create site search pages, I pretty much always end up duplicating the same features from site to site. Also – since it takes a bit of extra time – it's tempting to skip over some accessibility related things, and leave features like text highlighting out. Overall I think it makes sense to bundle all that into a module, which can then be reused over and over again 🙂
      Note: markup generation is not yet built into the module, which is why the examples below use PageArray::render() method to produce a simple list of results. This will be added later on, as a part of the same module or a separate Markup module. There's also no fancy JS API or anything like that (yet).
      This is an early release, so be kind – I got the find feature working last night (or perhaps this morning), and some final tweaks and updates were made just an hour ago 😅
      GitHub repository: https://github.com/teppokoivula/SearchEngine Modules directory: https://modules.processwire.com/modules/search-engine/ Demo: https://wireframe-framework.com/search/ Usage
      Install SearchEngine module. Note: the module will automatically create an index field install time, so be sure to define a custom field (via site config) before installation if you don't want it to be called "search_index". You can change the field name later as well, but you'll have to update the "index_field" option in site config or module settings (in Admin) after renaming it.
      Add the site search index field to templates you want to make searchable. Use selectors to query values in site search index. Note: you can use any operator for your selectors, you will likely find the '=' and '%=' operators most useful here. You can read more about selector operators from ProcessWire's documentation.
      Options
      By default the module will create a search index field called 'search_index' and store values from Page fields title, headline, summary, and body to said index field when a page is saved. You can modify this behaviour (field name and/or indexed page fields) either via the Module config screen in the PocessWire Admin, or by defining $config->SearchEngine array in your site config file or other applicable location:
      $config->SearchEngine = [ 'index_field' => 'search_index', 'indexed_fields' => [ 'title', 'headline', 'summary', 'body', ], 'prefixes' => [ 'link' => 'link:', ], 'find_args' => [ 'limit' => 25, 'sort' => 'sort', 'operator' => '%=', 'query_param' => null, 'selector_extra' => '', ], ]; You can access the search index field just like any other ProcessWire field with selectors:
      if ($q = $sanitizer->selectorValue($input->get->q)) { $results = $pages->find('search_index%=' . $query_string . ', limit=25'); echo $results->render(); echo $results->renderPager(); } Alternatively you can delegate the find operation to the SearchEngine module as well:
      $query = $modules->get('SearchEngine')->find($input->get->q); echo $query->resultsString; // alias for $query->results->render() echo $query->pager; // alias for $query->results->renderPager() Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 Note: later versions of the module may require Composer, or alternatively some additional features may require installing via Composer. This is still under consideration – so far there's nothing here that would really depend on it, but advanced features like stemming most likely would.
      Installing
      It's the usual thing: download or clone the SearchEngine directory into your /site/modules/ directory and install via Admin. Alternatively you can install SearchEngine with Composer by executing composer require teppokoivula/search-engine in your site directory.
    • By teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if someone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put I've been using MSN (...) for years, and it's been great – but there are some issues with it, particularly in the markup generation area, and it also does some things in a way that doesn't quite work for me – the xtemplates thing being one of these. In some ways less about features, and more about style, I guess 🙂
      Anyhow, in MarkupMenu I've tried to correct those little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and with PHP 7.1+ in mind, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) still on my todo list.
      One more small(ish) difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site had a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to leave that out 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM – one of those three or four letter abbreviations anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework" since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
×
×
  • Create New...