This is actually just in a _block I've created, it's my sidebar. It's loaded in on each view with:
<?php $this->load->view('_blocks/sidebar', $sidebar); ?>
$sidebar isn't related to the newsletter, as it's an array of data containing t…
Okay, I'll have to do that. Thanks.
Although now the original issue is back, and I can't see what I've changed. I'm using:
echo form('newsletter');
Although, if I use:
$form = $this->fuel->forms->create('newsletter'); echo $form->ren…
Okay, fixing the issue in the other thread seems to have solved this one too. Coming back to re-create it it seems to be working. So, thanks for the help but I can't reproduce it any more.
On the newsletter though, I have one more question. I'm lin…
Yep, I'm up to date with develop
Yes this does fix it. I also had to make this change on all instances of _tables into _parent_model->tables() in the get_author function too.
This also appears in get_comments, but I can go to a blog post page …
Haha okay, I'm not sure where I would echo that 'boo' out if you follow me. The URL stays the same, and after I've submitted the form the page refreshes and I'm left with:
Here's before the form submit, and after: https://imgur.com/a/j4Giy
I'm o…
Your Projects model would look something like the above, and your Customers model would look something like this:
<?php if (!defined('BASEPATH')) exit('No direct script access allowed'); require_once(FUEL_PATH.'models/base_module_model.php'); …
Great, thank you! Can confirm it's working. Although on this subject, is there a way to disable email notifications site wide? We don't have a mail server set up so the last error ("Failed to connect to mailserver..") comes up still.
You can assign a has many relationship to your models with a $has_many variable. For example, your model would look something like this:
<?php if (!defined('BASEPATH')) exit('No direct script access allowed'); require_once(FUEL_PATH.'models/ba…
I'm also getting
A PHP ERROR WAS ENCOUNTERED Severity: Notice Message: Undefined index: comments Filename: models/blog_posts_model.php Line Number: 470 A PHP ERROR WAS ENCOUNTERED Severity: Warning Message: Invalid argument supplied for foreach() F…
Okay I've figured it out, although I still have an issue.
The original problem was the way I was calling the data.
Instead of $vars['sidebar']['recent_posts'] = $sidebar_model->recent_posts; I should be doing $vars['sidebar']['recent_posts'] = …
Well, I'm using fuel_model to get the data from fuel, and also the fuel_blog module $recent_posts = $this->_CI->fuel_blog->get_recent_posts(3);. Is that what you mean by using fuel? Because if so, then yes
I'm already on the develop branch actually, I've forked the module and running my own develop branch which is up to date (well, technically infront ) of the upstream branch.
$ git merge upstream/develop Already up-to-date.
I ran fuel_blog_uninstal…
So this was an issue with either PHP or Apache. They were behind by a few minor versions so I've just updated them and I'm not running into this issue anymore.
thanks!
Oh, I didn't realise the SQL updates were different. I switched branches on the blog submodule, and didn't run through those updates.
ran the uninstall.sql from the master branch, then ran both install sql files from https://github.com/daylightstud…
Oh great, thanks! I'm up to date on develop in both fuel and blog, and the error has gone and I can now successfully post as a super admin. Although posting as a regular user I see no posts at all when on the /blog/posts view, it just says "No data …
Hey,
Thanks for the quick update! I'm still getting a bit of an issue though. I now get this when creating a new blog post as a super-admin:
A Database Error Occurred Error Number: 1054 Unknown column 'fuel_users.first_name' in 'field list' S…
Oh excuse me, I thought you were talking about the Fuel repo and I was already on the develop branch for that. I've switched over to the blog module branch develop although I've ran into something.
With settings > blog > limit to user selecte…
Ah okay, nice! I can follow that, although I didn't notice the "User" field before, and imo it seems a bit more powerful to have Users and assign Authors to them anyway (so you can have some Authors with Users with access to certain Authors and also…