Re: [bedita@google] Digest for bedita@googlegroups.com - 3 Messages in 1 Topic

[Gianluca Isaia]

Thank you for your help. Tha matter was with htacces. I solved it. Now I play a little before to quote.

2012/9/18 <bed...@googlegroups.com>

  Today's Topic Summary

Group: http://groups.google.com/group/bedita/topics

• Missing Foldler [3 Updates]

 Missing Foldler

Gianluca Isaia <isaiag...@gmail.com> Sep 17 05:36PM +0200  

After the installation I had attempt to login and this is the matter that I
have encountered after the login.
 
 
The requested URL /bedita/authentications/login was not found on this
server
 
After a control I discovery that authentications folder missing too.
 
I tried with the 3.2 too. Same matter.
 
Can you help me?
 
I'm Italian if you prefer to write in my mother tongue answer in Italian
 
If you prefer that I post this message to the group page order and I do it.
(xd)
 
Thank you for attention.


 

Dante <didoj...@gmail.com> Sep 17 11:05PM -0700  

Hi Gianluca,
thanks for trying BEdita!
 
It seemed that something went wrong with your setup.
 
Could you please tell us something more about your environment (php
version, mysql version, apache version [I suppose you use apache], etc.)?
 
If I could bet, I'd say that you faced a "mod_rewrite" issue.
Did you notice something "strange" in your local bedita login page? maybe a
page without stylesheets?
In that case, it means that you don't have mod_rewrite enabled on your
system.
If you have a 'mod_rewrite' issue, you can decide to do one of the
following:
 
a) enable mod_rewrite on your webserver (apache or other)
 
OR
 
b) disable mod_rewrite on $BEDITA_HOME/bedita_app/config/core.php; in this
file you uncomment the line that looks like:
Configure::write(‘App.baseUrl’, env(‘SCRIPT_NAME’)); then you remove
.htaccess files: $BEDITA_HOME/.htaccess, $BEDITA_HOME/bedita-app/.htaccess
and $BEDITA_HOME/bedita_app/webroot/.htaccess
 
If you a different problem, it's necessary to take a look at logs of bedita
and logs of your server, to understand what's going on.
Maybe you could try from here:
http://docs.bedita.com/setup/if-something-goes-wrong-in-bedita (a doc about
common issues after bedita install).
 
Recently we passed BEdita on github. If you want to try to install from
there, take a look at this article:
http://docs.bedita.com/setup/install-bedita-3-2
 
I hope that I helped you. Let us know if you succeed with your bedita
install ;)
 
Ciao,
Dante.
 
On Monday, September 17, 2012 5:36:48 PM UTC+2, Icser wrote:


 

Dante <didoj...@gmail.com> Sep 17 11:18PM -0700  

ehm, I forgot to say where to find 'bedita on github'; if you are
interested, look here: https://github.com/bedita/bedita
 
ciao,
dante.
 
On Monday, September 17, 2012 5:36:48 PM UTC+2, Icser wrote:


 

You received this message because you are subscribed to the Google Group bedita.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

[Icser]

I Dante to comply with cake-php and my host rules I have added RewriteBase to all the .htaccess but something go wrong yet.
And that the matter http://prntscr.com/h0r26
The .htacces in bedita is
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteBase /bedita/
RewriteRule ^$ bedita-app/webroot/ [L]
RewriteRule (.*) bedita-app/webroot/$1 [L]
</IfModule>
Some suggestion?

[Dante]

Hi,
    some questions before going on:

1.) which version of bedita are you trying to use (3.1 or 3.2?)?
2.) is mod_rewrite enabled on your environment?

You edit one .htaccess file, but there are still 2 more .htaccess files (in bedita-app and bedita-app/webroot folder).
Recently we wrote an article about 'handling mod_rewrite': http://docs.bedita.com/setup/handling-mod_rewrite-in-bedita-and-cakephp
Did you already check it? It contains useful informations ;)
Regards,

Dante

[Icser]

1) I can't access by shell so I choose 3.2 populus
2) Yes is enabled

Of course I edit the other this is my work:

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteBase /bedita/bedita-app/
RewriteRule ^$ webroot/ [L]
RewriteRule (.*) webroot/$1 [L]
</IfModule>

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /bedita/bedita-app/webroot/
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ index.php?url=$1 [QSA,L]
</IfModule>

Yes Dante I read it and this http://book.cakephp.org/1.3/view/917/Apache-and-mod_rewrite-and-htaccess http://httpd.apache.org/docs/current/mod/mod_rewrite.html

but I can't find a solution.

This is the .htaccess before the /htdcos but I can't modify it. I suppose that can is it the matter:

ErrorDocument 403 /__tmp/topweb.shtml
AddHandler php5-script .php

Icser

[Alberto Pagliarini]

Hi,

it seems very very strange. BEdita use get_headers() php function to test beditaUrl and mediaUrl.

On my machine I have tried:

<?php

echo "<pre>";

print_r(get_headers("http://www.toolics.com/bedita/"));

print_r(get_headers("http://www.toolics.com/bedita/bedita-app/webroot/files"));

echo "</pre>";

?>

and the response are reachable

Array

(

    [0] => HTTP/1.1 200 OK

    [1] => Date: Mon, 08 Oct 2012 13:18:33 GMT

    [2] => Server: Apache

    [3] => X-Powered-By: PHP/5.3.3-7+squeeze1

    [4] => P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"

    [5] => Set-Cookie: CAKEPHP=630ccfbb93b226e86391f11578842f02; expires=Sun, 10-Feb-2013 13:18:34 GMT; path=/bedita/bedita-app

    [6] => Vary: Accept-Encoding

    [7] => Connection: close

    [8] => Content-Type: text/html

)

Array

(

    [0] => HTTP/1.1 301 Moved Permanently

    [1] => Date: Mon, 08 Oct 2012 13:18:34 GMT

    [2] => Server: Apache

    [3] => Location: http://www.toolics.com/bedita/bedita-app/webroot/files/

    [4] => Vary: Accept-Encoding

    [5] => Content-Length: 328

    [6] => Connection: close

    [7] => Content-Type: text/html; charset=iso-8859-1

    [8] => HTTP/1.1 403 Forbidden

    [9] => Date: Mon, 08 Oct 2012 13:18:34 GMT

    [10] => Server: Apache

    [11] => Content-Location: topweb.shtml.en.shtml

    [12] => Vary: negotiate,accept-language,Accept-Encoding

    [13] => TCN: choice

    [14] => Accept-Ranges: bytes

    [15] => Connection: close

    [16] => Content-Type: text/html

    [17] => Content-Language: en

)

BEdita checks the first item of each array and throw an error if the response is a 4xx or 5xx http error. As you can see the first item is HTTP/1.1 200 OK and HTTP/1.1 301 Moved Permanently. No error should be thrown.

I tested also to insert your configuration url in my local BEdita instance and no error was thrown.

Can you test on your server the little script I wrote above and see what is the response?

Anyway, you should be able to use BEdita also with those warning messages. Try to upload an image in Multimedia module, if you can see the thumbnail then your mediaUrl configuration is ok.

alberto

2012/10/8 Icser <isaiag...@gmail.com>

--
------ bato -------

[Dante]

Hi,

    I tried now to open http://www.toolics.com/ops.php and http://www.toolics.com/bedita/
In both cases, no warnings, no errors.
In http://www.toolics.com/ops.php I see the two arrays described by alberto, in http://www.toolics.com/bedita/ I see bedita login page.

Maybe you are under an internal proxy and browser rules/behaviour to open www.toolics.com change. Is it possible?
(or www.toolics.com is somehow set in your hosts local machine).

You can set debug level to zero, if you don't want to see warnings (bedita/bedita-app/config/core.php => Configure::write('debug',0);)

Try to follow the 4 tips in http://docs.bedita.com/setup/if-something-goes-wrong-in-bedita

1 Set debug level to '1'
2 Take a loog at BEdita logs
3 Take a look at apache logs (supposing that your webserver is apache)

If you find errors among logs, it could help to solve. Let us know ;)

Dante.


Il giorno lunedì 8 ottobre 2012 15:59:45 UTC+2, Icser ha scritto:

That the answer

Warning:  get_headers() [function.get-headers]: http:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/mhd-01/www.toolics.com/htdocs/ops.php on line 3

Warning:  get_headers() [function.get-headers]: This function may only be used against URLs in /home/mhd-01/www.toolics.com/htdocs/ops.php on line 3

Warning:  get_headers() [function.get-headers]: http:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/mhd-01/www.toolics.com/htdocs/ops.php on line 4

Warning:  get_headers() [function.get-headers]: This function may only be used against URLs in /home/mhd-01/www.toolics.com/htdocs/ops.php on line

[Alberto Pagliarini]

You could also try to disable mod rewrite removing all .htaccess files and uncommenting the relative row in bedita-app/config/core.php

Il giorno 08/ott/2012 16:14, "Icser" <isaiag...@gmail.com> ha scritto:

No I can't use it. Frontend don't run well (no response for the link. it stop to first section) In Backend>pubblication don't appare the link to publication and section.

Tanks for your patient Icser

[Icser]

Thank you BEdita staff. It run. Now the world can BE wonderful.

[Alberto Pagliarini]

Well done!

We are glad that your BEdita installation works well!

For curiosity, how have you solved?

2012/10/9 Icser <isaiag...@gmail.com>

Thank you BEdita staff. It run. Now the world can BE wonderful.

--
------ bato -------

[Icser]

Allow url fopen that's all.

[Icser]

HI bato here I tried to install ulmus. Can you say about it. Of course here I have matter. Sorry to claim your help another time. .htacces ok mod rewrite on allow url fopen on.

./cake.sh bedita init

BEdita CLEANUP
Cache cleaned.
Smarty compiled/cache cleaned.
---------------------------------------------------------------
CHECKING DATABASE CONNECTION
Checking database connection: default - mysql [host=localhost, database=bedb]
Database connection: ok
---------------------------------------------------------------

---------------------------------------------------------------
CHECKING MEDIA ROOT
/var/www/html/straics/xcart/bedita/./bedita-app/webroot/files - perms: 775
---------------------------------------------------------------
CHECKING MEDIA URLs
http://95.110.157.144/bedita/bedita-app/webroot/files: ok.
---------------------------------------------------------------

---------------------------------------------------------------
INITIALIZE DATABASE
Updating bedita db config: default - mysql [host=localhost, database=bedb]
ACHTUNG! Database bedb will be replaced, proceed? [y/n]
> y
---------------------------------------------------------------
Update schema from /var/www/html/straics/xcart/bedita/./bedita-app/config/sql/bedita_mysql_schema.sql
Load data from /var/www/html/straics/xcart/bedita/./bedita-app/config/sql/bedita_init_data.sql
default database updated
checking media files
checkMedia - checking database
checkMedia - database OK

BEdita STATUS
---------------------------------------------------------------
Checking backend app dir: bedita-app
---------------------------------------------------------------
bedita-app/config/core.php: ok.
bedita-app/config/database.php: ok.
bedita-app/config/bedita.sys.php: ok.
bedita-app/config/bedita.cfg.php: ok.
bedita-app/index.php: ok.
bedita-app/webroot/index.php: ok.
bedita-app/webroot/test.php: ok.
bedita-app/tmp/cache - perms: 775
bedita-app/tmp/smarty/compile - perms: 775
bedita-app/tmp/logs - perms: 775
---------------------------------------------------------------
Checking frontend app dir: /var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com
---------------------------------------------------------------
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com/config/core.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com/config/database.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com/webroot/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com/tmp/cache - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com/tmp/smarty/compile - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/debug.example.com/tmp/logs - perms: 755
---------------------------------------------------------------
Checking frontend app dir: /var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com
---------------------------------------------------------------
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com/config/core.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com/config/database.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com/webroot/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com/tmp/cache - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com/tmp/smarty/compile - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/dummy.example.com/tmp/logs - perms: 755
---------------------------------------------------------------
Checking frontend app dir: /var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com
---------------------------------------------------------------
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com/config/core.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com/config/database.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com/webroot/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com/tmp/cache - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com/tmp/smarty/compile - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/html5.example.com/tmp/logs - perms: 755
---------------------------------------------------------------
Checking frontend app dir: /var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com
---------------------------------------------------------------
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com/config/core.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com/config/database.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com/webroot/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com/tmp/cache - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com/tmp/smarty/compile - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/site.example.com/tmp/logs - perms: 755
---------------------------------------------------------------
Checking frontend app dir: /var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com
---------------------------------------------------------------
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com/config/core.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com/config/database.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com/webroot/index.php: ok.
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com/tmp/cache - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com/tmp/smarty/compile - perms: 755
/var/www/html/straics/xcart/bedita/./bedita-app/../frontends/wp.example.com/tmp/logs - perms: 755
---------------------------------------------------------------
Checking media dir and url
---------------------------------------------------------------
mediaRoot: /var/www/html/straics/xcart/bedita/./bedita-app/webroot/files - perms: 775
mediaUrl: http://95.110.157.144/bedita/bedita-app/webroot/files: ok.
beditaUrl: http://95.110.157.144/bedita: ok.
Checking database connection: default - mysql [host=localhost, database=bedb]
Database connection: ok
Cake debug level: 1
Cake session handling: database
Using mod_rewrite

Array
(
[0] => HTTP/1.1 200 OK

[1] => Date: Fri, 12 Oct 2012 06:37:45 GMT
[2] => Server: Apache
[3] => Expires: Fri Oct 12 06:42:45 2012 GMT
[4] => Cache-Control: private, max-age=300, must-revalidate
[5] => P3P: CP="NON DSP COR DEVa PSAa PSDa OUR IND UNI COM", policyref="http://www.cnet.com/w3c/p3p.xml"
[6] => Connection: close
[7] => Content-Type: text/html; charset=utf-8

)
Array
(
[0] => HTTP/1.1 301 Moved Permanently

[1] => Date: Fri, 12 Oct 2012 06:37:05 GMT
[2] => Server: Apache/2.2.15 (CentOS)
[3] => Location: http://www.straics.com/bedita/bedita-app/webroot/files/
[4] => Content-Length: 344
[5] => Connection: close
[6] => Content-Type: text/html; charset=iso-8859-1
[7] => HTTP/1.1 200 OK
[8] => Date: Fri, 12 Oct 2012 06:37:05 GMT
[9] => Server: Apache/2.2.15 (CentOS)
[10] => Content-Length: 788
[11] => Connection: close
[12] => Content-Type: text/html;charset=UTF-8
)

[bato]

Hi Icser,

in BEdita 3.1 ulmus installation

Using mod_rewrite

is just an information on your mod_rewrite configuration in bedita-app/config/core.php. No check on apache module is done. I suggest you to check your apache configuration and verify that mod_rewrite is enabled. You can also see that with

<?php

phpinfo();

?>

searching "mod_rewrite"

Alberto

[Icser]

Thank you bato

The mod_rewrite is enabled

[Icser]

No BEpeople you can't have relax with me.
There is some matter in my populus installation. When I delete a comment Bedita delete the relative document too, but not from the database, only link from frontends and relative object(not the link) from the backend.Another sign that something was gone wrong it's the assence of the publication and section tree in the left area of publication page ( talking about backend).
Another strange thing is that I can login in the frontend but not logout.

Thanks for your attention.

Ciao
Icser

[bato]

Il giorno martedì 16 ottobre 2012 09:50:11 UTC+2, Icser ha scritto:

There is some matter in my populus installation. When I delete a comment Bedita delete the relative document too, but not from the database, only link from frontends and relative object(not the link) from the backend.

I can't reproduce the error. What frontend are you using? I made some test wit wp.example.com:

1. added document with "comments" flag on "yes" to a section
2. in frontend I posted a comment related to document above
3. in backend I deleted the comment
4. in frontend and in backend I still see  the document in the right place

Missing something? If so, could you illustrate it step by step

 

Another sign that something was gone wrong it's the assence of the publication and section tree in the left area of publication page ( talking about backend).

yes it's very strange... in your mysql installation is enabled innodb support? If it isn't you need to enable it otherwise bedita not work well.

 

Another strange thing is that I can login in the frontend but not logout.

Logout doesn't work?? Or in your frontend is missing logout link?

ciao

alberto

[Icser]

Il giorno martedì 16 ottobre 2012 11:13:04 UTC+2, bato ha scritto:
> Il giorno martedì 16 ottobre 2012 09:50:11 UTC+2, Icser ha scritto:There is some matter in my populus installation. When I delete a comment Bedita delete the relative document too, but not from the database, only link from frontends and relative object(not the link) from the backend.
>
>
> I can't reproduce the error. What frontend are you using? I made some test wit wp.example.com:

> added document with "comments" flag on "yes" to a sectionin frontend I posted a comment related to document abovein backend I deleted the commentin frontend and in backend I still see the document in the right place

> Missing something? If so, could you illustrate it step by step

The site is site.example.com
Added document with "comments" flag on "yes" to a section in backend
I posted a comment related to document above in frontend
I deleted the comment in backend. Assuming that it is deleted from frontend too.
The comment was deleted.
(matter)The relative document was deleted in frontend
Link to the document appears in backend document section
The document data are stored in database yet
(matter) I click the above link in backend, message error inform me that the object was not found

> Another sign that something was gone wrong it's the assence of the publication and section tree in the left area of publication page ( talking about backend).
>
>
>
> yes it's very strange... in your mysql installation is enabled innodb support? If it isn't you need to enable it otherwise bedita not work well.
> Another strange thing is that I can login in the frontend but not logout.
>

>Here you suggest the right solution... now I hope to reach it.

>
> Logout doesn't work?? Or in your frontend is missing logout link?

There isn't the link in frontend

[bato]

Tested on site.example.com

Il giorno martedì 16 ottobre 2012 16:23:58 UTC+2, Icser ha scritto:

The site is site.example.com
Added document with "comments" flag on "yes" to a section in backend
I posted a comment related to document above in frontend
I deleted the comment in backend. Assuming that it is deleted from frontend too.
The comment was deleted.
(matter)The relative document was deleted in frontend

no happens to me, the document is present in frontend

 

Link to the document appears in backend document section
The document data are stored in database yet
(matter) I click the above link in backend, message error inform me that the object was not found

no happens to me. The document is linked correctly.

It may be due to innodb engine issue. If your db haven't innodb enabled, enable it then you have to initialize the db again. When done retry and let we know if it's work well.

 There isn't the link in frontend

well,  *.example.com are intended to be as example frontends. Could missing some funtionality. But you can add easily a logout link that has to be redirect to

site.example.com/logout

try also to write that url in your address bar and you'll see that logout will be performed.

cheers

alberto