timnboys

Fixed Hidden Forums Issue, now forums that are hidden will stay hidden from main index and will only be accessible by people who know the link to them.

Link Redacted for Security Reasons.

technically the trial download isn't working because it hasn't been released to the public yet(aka reached RC(Release Candidate) status yet)

you have to have a owned blesta license for buying the license manager.
to quote paul:
 

There's many factors that are involved in the pricing of modules/plugins such as API Documentation, Features, Amount of time, and much more. 
Your best bet is to request quotes from a few developers for hire and compare and make a decision. You can find a list here. When submitting a request for a quote from someone please be as specific as possible. List every detail you require in the project so that it can be as accurate as possible.

PM answered 

so how is development going mike? haven't heard anything on development and when we are able to use it on our own blesta installation yet mike. Got anymore development updates? 
@Blesta.Store

I fully recommend using the REMI packages they seem to have included the mailparse extension with there php extensions which makes it 100% more easier to build up a new vm with blesta on it.

I fully recommend using the REMI packages they seem to have included the mailparse extension with there php extensions which makes it 100% more easier to build up a new vm with blesta on it.

have you tried enabling your debug mode inside blesta's config to see why?
that would log the errors in your webserver log otherwise blesta will try to "mask" the errors instead and you will not see them in the error log of your webserver.

have you tried enabling your debug mode inside blesta's config to see why?
that would log the errors in your webserver log otherwise blesta will try to "mask" the errors instead and you will not see them in the error log of your webserver.

I fixed the bug by doing this in direct_admin_api.php:
'suspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Suspend','location'=>'CMD_API_SELECT_USERS')), 'unsuspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Unsuspend','location'=>'CMD_API_SELECT_USERS')), from:
'suspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Suspend','location'=>'CMD_SELECT_USERS')), 'unsuspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Unsuspend','location'=>'CMD_SELECT_USERS')), that was likely a oversight on the blesta dev's part but is actually easily to fix as shown above, since directadmin's api information here:
http://www.directadmin.com/features.php?id=807
states the default CMD_SELECT_USERS will not return the standard json api response like the module is expecting, CMD_API_SELECT_USERS does return the standard json api response and therefore it works finally, tried to find the module on github to submit a pull request to apply this patch to module but didn't find it so thought would just post it here instead.


thanks to @Doctrine for providing the directadmin panel to patch the issue and make sure it works.
information redacted for security reasons.

just to update everyone the lines have changed a bit in blesta v4.2
plugins/support_manager/models/support_manager_tickets.php
 
Add after Line 300:
where("support_tickets.status", "!=", "on_hold")->
 
Add after Line 1200:
'on_hold' => $this->_("SupportManagerTickets.status.on_hold"),
the rest is the same as above in op.

I fixed the bug by doing this in direct_admin_api.php:
'suspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Suspend','location'=>'CMD_API_SELECT_USERS')), 'unsuspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Unsuspend','location'=>'CMD_API_SELECT_USERS')), from:
'suspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Suspend','location'=>'CMD_SELECT_USERS')), 'unsuspendUser' => array('POST','','CMD_API_SELECT_USERS',array('suspend'=>'Unsuspend','location'=>'CMD_SELECT_USERS')), that was likely a oversight on the blesta dev's part but is actually easily to fix as shown above, since directadmin's api information here:
http://www.directadmin.com/features.php?id=807
states the default CMD_SELECT_USERS will not return the standard json api response like the module is expecting, CMD_API_SELECT_USERS does return the standard json api response and therefore it works finally, tried to find the module on github to submit a pull request to apply this patch to module but didn't find it so thought would just post it here instead.


thanks to @Doctrine for providing the directadmin panel to patch the issue and make sure it works.
information redacted for security reasons.

I know it is a different plugin to the cms but it is something that I thought was missing to start with since if you have the cms but no forum you are missing something important in my opinion considering not every host wants to have a external forum to have to work out SSO with blesta for especially if you are using your cms mike as I have found out with modx integrating SSO with blesta is harder than it looks and at this point would rather just have it all integrated and not have to build custom SSO bridges,etc to make modx and blesta talk to each other. since with the cms and this forum plugin it would share logins with blesta and therefore make SSO(single sign on) even easier which is why I said at this point I am looking for easy solutions not having to build both a modx plugin for SSO to integrate sharing logins between modx<->blesta. 

great! this means I can move back to blestacms soon to have my own forums I had to move to modx for.

okay great, would be looking forward to beta test or get the plugin on release because I would like to pair blestacms and blestaforums together and move back from modx lol 

that is sounding like you are looking for a way to rewrite the url so for example if announcements is forum id one it shows as {blestaroot}/plugin/blestaforums/forum/1/ correct? if so that sounds like some sort of route or rewrite you would have to tell blesta about.
I would recommend in your forum controller php file mike to put what cyandark showed in your index function as such:
class Forum extends MyPluginController { ..... public function index() { if (!empty($this->get[0]) && is_numeric($this->get[0])) { $page_id = $this->get[0]; } else { $page_id = 1; } // Load forum model Loader::loadModels($this, ['MyPlugin.ForumsFunctions']); // Get forum page $forum = $this->ForumsFunctions->getForum($page_id); } .... } put the above in your index function for your forum controller and yes it will show up with the structure you want in the url.
eg this structure:
http://awesomecompany.com/client/plugin/my_plugin/forum/1/
that would get the forum id 1 as shown in the example url like you want.
do note the .... is to be your existing code don't copy the .'s please they have no real purpose other than being a placeholder for your other code. 

that sounds like what I did similar to that in my vultr module to grab the saved plan from the db to be selected by default in the dropdown select box on editing a package 
I would "fish" the code out I used to do that but I don't think it is relevant to what mike is trying to do since he wants to do exactly as you described @cyandark because mine was for a module this is probably in relation to mike's blestaforums plugin. 

you have got me interested mike, this is something I felt like was missing so you could use both blestacms + a forum on blesta as well integrated with blesta+blestacms so I would like to be a beta tester as well or buy the license when it comes out if it isn't too expensive.

you have got me interested mike, this is something I felt like was missing so you could use both blestacms + a forum on blesta as well integrated with blesta+blestacms so I would like to be a beta tester as well or buy the license when it comes out if it isn't too expensive.

that is sad to hear everyone is having to move back to the dark side of whmcs or some other panel because of domain manager features not being added yet. this is sad though since I would hate to see everyone having to find other options 

that is sad to hear everyone is having to move back to the dark side of whmcs or some other panel because of domain manager features not being added yet. this is sad though since I would hate to see everyone having to find other options 

that is sad to hear everyone is having to move back to the dark side of whmcs or some other panel because of domain manager features not being added yet. this is sad though since I would hate to see everyone having to find other options 

well I like how the fraud check works currently since my anti fraud module I have it set to run each time a new order/client signs up and I want it to trip on any incomplete forms and non-payments to block and reject anyone it finds suspicious. though I would be open to providing @camgullo and you @MineHarvest66 with a free owned license of my anti fraud module since it checks both for fraudrecord reports & vpn/tor/etc checks as well since I have used fraudlabs pro before and can tell how fast the free plan credits disappears and it is not just on blesta that I have seen it happen also on whmcs which I used to use, as well which is why I set out and built my own anti fraud module to resolve this for myself.

your license has already been issued to your account in my blesta.
@MineHarvest66 I sent you a pm asking if you was in my blesta or not as it is kinda hard to issue licenses to non existing accounts