Jump to content

Recommended Posts

I'm signed-in as admin with guest, superuser roles, but cannot edit any content within Body or Sidebar. This is despite the Access page apparently showing I have permission to do all this.

I'm really keen to get started with PW, but this is extremely frustrating.

Share this post


Link to post
Share on other sites

Welcome to ProcessWire.  Can you provide a little more information regarding your site setup/structure so someone can help you?

Share this post


Link to post
Share on other sites

Hello cstevensjr, thank you.

Running current version of PW with the 'demo' skyscraper content locally on Windows 7 with current version of XAMMP. Anything else you need?

P.S.

This is an 'out-of-the-box install, no additional modules added or custom changes made.

Share this post


Link to post
Share on other sites

Probably not. If you can, make a screenshot of a page where you cannot edit content. How do you know you can't edit? The textarea is inactive? You got some sort of message while saving a page?

Share this post


Link to post
Share on other sites

Hello Ivan.

Yes, the the textarea is inactive. It appears to me as if I simply have insufficient permissions though every setting tells me otherwise.

Share this post


Link to post
Share on other sites

This is very weird. Try to edit the summary. Can you safe what you write in there? If so, something might be broken/corrupt with your body and/or sidebar fields. Try to replace them. If you can't safe the page at all, report back please.

EDIT: Have you checked your server environment? (https://github.com/ryancramerdesign/ProcessWire#troubleshooting-installation) Is your site/config.php and site/templates writeable?

Share this post


Link to post
Share on other sites

Maybe javascript is turned off?
It seems that only TinyMCE fields do not work. They should fallback to textarea, but check anyway.

  • Like 3

Share this post


Link to post
Share on other sites

Hi totoff.

Yes I can edit and save Summary and Title.

As this is clearly not a common problem, perhaps I should just download a new package and try another clean install. I'll save this template set to compare later. If all goes ok on second install, I may be able to determin the cause. I shall do this a little later on today and report back. Thanks all.


Ivan: JavaScript is running.

Share this post


Link to post
Share on other sites

Maybe its in demo mode.. look in site/config.php

Share this post


Link to post
Share on other sites

It's like Ivan said: Looks like a TinyMCE problem.

Do you tried different Browsers? Which OS are you running (looks like windows 2000)? Have you tried to use another computer? 

  • Like 1

Share this post


Link to post
Share on other sites

If you are using Chrome, check the console output to see if there are errors

Share this post


Link to post
Share on other sites

It's like Ivan said: Looks like a TinyMCE problem.

Do you tried different Browsers? Which OS are you running (looks like windows 2000)? Have you tried to use another computer? 

Tried in Opera - an old Presto build ironically - and et voila :)

So it was a browser issue all along. Why didn't I check that?

Many thanks Nico. I shall now try to work out why this was the case at localhost, but not at the PW online demo, which rendered perfectly.

For future reference my main browser - since Opera committed suicide - is PaleMoon, a custom build of Firefox. Though that in itself is clearly not the sole cause. I

Many thanks to everyone for being so helpful. Glad I don't have cause to blame PW for this initial glitch, because it appears to be the ideal bloat-free, common sense CMS solution I've been searching for.

  • Like 1

Share this post


Link to post
Share on other sites

If you are using Chrome, check the console output to see if there are errors

Yes I should have done more investigation browser-wise, but it was that the online demo that worked perfectly that threw me!

Share this post


Link to post
Share on other sites

Just to tie things up....

The lack of editing options was due to127.0.0.1/ProcessWire/wire/modules/Inputfield/InputfieldTinyMCE/tinymce-3.5.8/plugins/inlinepopups/editor_plugin.js prevented from loading. The culprit was the following badly implemented regex in my custom adblock script:  .popup.*\.js  Either a typo or accidentally left in place after some testing. Removed it and everything is dandy! TinyMCE editing returned to normal. Now I can get on and enjoy PW. Thanks again all :)

I take full responsibility for my clumsiness. :-[

  • Like 1

Share this post


Link to post
Share on other sites

since Opera committed suicide

this is, btw, true and sad at the same time.

  • Like 1

Share this post


Link to post
Share on other sites

this is, btw, true and sad at the same time.

Very sad indeed totoff. I miss Opera/Presto ever second I'm online. Nothing else comes close. :(

I've done my best to replicate most of the functionality with numerous plugins and PaleMoon (Firefox), but I just can't achieve the same contented, secure feeling I always had with Opera/Presto. Opera/Presto was solid and they just threw all away in favour of a re-badged Chrome. Opera ASA never gave a single thought for it's devoted user base. It's a tragic waste. Don't let me get started. >:D

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By humanafterall
      Hi,
      I would like to set an admin template to 'https only' as recommended in the Processwire security docs.
      However if I do this it forces this setting locally too, resulting in https://localhost requests which result in an error page.
      Is there a simple way round this? Setting https for templates in the config?
      Thanks!
    • By theoretic
      Hi guys and ladies! And thanks for Processwire!
      It appears i've got an interesting issue concerning the template-settings-based PW redirects dealing with access control. Any PW template has some access control options i.e. "Login redirect URL or page ID to render". If this option is used for a page having a template with this option filled, a redirect will occur if user is not logged in and/or has insufficient access rights.
      I like to hook PW events. In one of my current projects i decided to write an addHookBefore('Session::redirect', ...) which should store the page we are being redirected from. With "regular" redirects like $session->redirect('/somewhere/') this hook works like a charm. But it was strange to see that it doesn't work with the template-settings-based redirect.
      I'm too dumb to dive deep inside PW and to examine the whole PW session mechanism. But it could be rather logical if ANY redirect ( no matter template-settings-based or using $session->redirect() ) could be hooked in the same manner.
      Okay okay i can forget about template-settings-based redirect and write my own. Just a couple of lines of code, and it works. But it's less elegant than hooking the template-settings-based redirects.
      So am i missing something? It this behavior a bug, or is it intended by PW team? Thanks in advance for any comment!
    • By DanielKit
      Hi. I'm currently stuck at the login page in my project. Once I enter my admin username and my password and press login, nothing happens. The page just reloads. However, the URL changes from http://myipaddress/processwire to http://myipaddress/processwire/?login=1. I've checked all of my server settings, and to my knowledge, all seems to be fine there. I don't know where to go from here.. Thanks in advance!
    • By VeiJari
      Hi, this is the first we are trying to make a page that has only one type of user that has access to every page. 
      The other users should only have a given access to specific pages, not to the whole template.
      My structure
      -Field -Organisation -Project -Report I want that the "measurer" role only has access to "project x" and it's children, but no view access to every project, organisation or field. I've tried to do this with https://modules.processwire.com/modules/page-edit-per-user/ but it still needs a view access to the whole tree to see the "project x" page. Or is there something I haven't figured out?
      Maybe I have to make it via the API: a select field in the "organisation" template where the admins could add the users and then I use hook to update the privileges?
      Have you done something like this and how did you accomplish it?
      Any help would be appreciated.
       
×
×
  • Create New...