Hi Jordan,

I think you found the problem.
It's true on my dev environment I use "localhost" and it's working.

Regards,
Pierre-Olivier

Jordan Michaels wrote:
> Hi Folks,
>
> Okay, Just this morning I was able to duplicate this on one of my own 
> installs. It appears to have to do with the domain name, oddly enough. 
> Whenever I used domain names like "localhost" or "server", it worked 
> fine. However, whenever I use a FQDN (www.mydomain.com), it errors out 
> with that permission error.
>
> When you tested it in the ready to run instance... did you use a FQDN or 
> did you use something like "localhost"?
>
> Just looking for some confirmation to save me some time from testing it 
> myself.
>
> Thanks!
>
> Warm regards,
> Jordan Michaels
> Vivio Technologies
> http://www.viviotech.net/
> Open BlueDragon Steering Committee
> Adobe Solution Provider
>
>
> Jordan Michaels wrote:
>   
>> Hi Magnus,
>>
>> I haven't been able to duplicate this in a test environment yet. When I 
>> use the installer on a blank slate VPS and then install BlogCFC, I can 
>> make test posts to it just fine.
>>
>> Do you know what version of the installer you used? The only thing I can 
>> figure is maybe it's related to a previous bug that has since been taken 
>> care of?
>>
>> If nothing else, I need to put together a new release anyway. The most 
>> recent OpenBD admin contains a patch that effects our customers ability 
>> to add email servers properly, and my techs are griping at me that they 
>> have to install it by hand. ;) Perhaps the most recent release will 
>> address this issue as well.
>>
>> Warm regards,
>> Jordan Michaels
>> Vivio Technologies
>> http://www.viviotech.net/
>> Open BlueDragon Steering Committee
>> Adobe Solution Provider
>>
>>
>> Magnus wrote:
>>     
>>> I moved the install I was having trouble with over to a windows
>>> machine that is running NA BD7 and it works fine. I haven't had a
>>> chance to work on the OpenBD version more since then but will pay
>>> around with it some more this weekend.
>>>
>>> Magnus
>>>
>>> On Mar 31, 10:01 am, Jordan Michaels <[email protected]> wrote:
>>>       
>>>> Heh... okay. I'm on it guys.
>>>>
>>>> Warm regards,
>>>> Jordan Michaels
>>>> Vivio Technologieshttp://www.viviotech.net/
>>>> Open BlueDragon Steering Committee
>>>> Adobe Solution Provider
>>>>
>>>> Pierre-Olivier Chassay wrote:
>>>>         
>>>>> Hi Matt,
>>>>> I just tested BlogCFC on Vista Machine with Tomcat/Apache and deploy
>>>>> only the war file OpenBD and everything works properly.
>>>>> Ok now we are sure it's an environment problem with Linux CentOS and
>>>>> OpenBD install with the last installer made by Jordan.
>>>>> Regards,
>>>>> Pierre-Olivier
>>>>> Matthew Woodward wrote:
>>>>>           
>>>>>> Pierre-Olivier Chassay wrote:
>>>>>>             
>>>>>>> I download the new release of BlogCFC(5.9.2.005) and still have the
>>>>>>> error with the cflogin roles="admin"
>>>>>>> The current user was not authorized to invoke this function
>>>>>>>               
>>>>>> To be clear, the latest BlogCFC version didn't implement anything new
>>>>>> related to roles. The fix was for another error that was being thrown
>>>>>> on the initial run on OpenBD (which was a bit of a mystery why it
>>>>>> wasn't also being thrown by CF).
>>>>>> What I was asking before is if you have tried BlogCFC on another
>>>>>> install of OpenBD, or are you still trying it in the environment where
>>>>>> you originally had the problem. If you could try it on the ready2run
>>>>>> version or a WAR deployment that would be helpful in at least
>>>>>> determining that it's an environment/specific install issue, which I
>>>>>> kind of suspect it is given the fact that I've run it in two different
>>>>>> environments with no problems.
>>>>>>             
>
> >
>   


--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official site @ http://www.openbluedragon.org/

!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to