Forum Replies Created

Viewing 10 replies - 46 through 55 (of 55 total)
  • @peter
    I think your use of the word ‘sterilized’ format was a Freudian slip. I think they are anything but sterile. I’m not an Apache expert but I think that the use of domain relative URLs has more to do with the way that PHP in the CMS constructs the reference(i.e it is ‘domain base address’ & ‘relative page reference’) rather than the server itself. I consider it a major flaw in WordPress.

    @mike
    Thanks for the clear explanation of the problem. Now if only the people at WordPress would follow the example of other systems like Drupal where the domain name is stored as a ‘base address’ system variable and doesn’t need to be stored with every reference…

    @aitpro
    I am getting similar PHP warning messages and the CAPTCHA image is broken. Can you tell me what the ‘better solution’ was?

    Maury

    You might look at the WP-Migrate DB plug-in. It will adjust the length of serialized data automatically as well as changing all the domain names. In my case it also allows me to dump my database without having to log in to the hosting site and using their PHPMyAdmin utility.

    Thread Starter mauryg

    (@mauryg)

    Removed Profile Builder and was able to update Group Documents to version 0.40 successfully. Verified conflict. Problem resolved.

    Same problem as Cynthiabee. Using UCP 1.0.09 with WP3.2.1, BP 1.5.1, child theme of Suffusion 3.9.5 and Suffusion BP Pack 1.06. When I try to add an image to a post (WYSIWYG editor = true) with either the Flash or browser uploader the image is uploaded into the media folder, but then I get a ‘white screen of death’. If I set ‘Force uploads Javascript’= true, I get a blank white pop up window like the WSOD. Text only uploads work.

    Also using WP Access Control for our MOSTLY members only site. Default setting for posts is ‘members only’. UCP does not obey this setting and all postings via UCP are ‘public’.

    Any ideas?

    I’m also using uCanPost and I don’t see why this was necessary. The plugin already lets you select the category for the post.

    Upon further testing I found that part of the problem is that QuickPostWidget is ROLE dependent. Or maybe it is just following WP role rules and only appears if it thinks the user has the rights to publish. Whatever the case the Quick Post page appears for Admin/Editor/Author roles but nothing below that. That’s OK if I can find that module that lets me define the rights for the different roles. Then I can simply set Members or Subscribers to be able to publish and it should work.
    In the meantime I discovered three other problems.
    1. If the user is an Author or Editor the Quick Post box will appear, but only the <Post Title> tag will be visible. The Content area does NOT allow you to enter any text. This is corrected by disabling the Visual Editor in the Quick Post options area. Then the <Post Content> tag appears and the content area will accept input. Unchecking the box in the options area removes the <Post Content> tag. This is reproducible.
    2. If the user (Author or Editor) publishes something and then clicks on the ‘Edit’ link in the post, they are taken to the backend WYSIWYG editor rather than to the Quick Post page. I want my members to be able to post news items but I don’t want them to be able to screw up the format/style of the site by all kinds of different fonts, etc so I don’t want them to have access to the WYSIWYG editor. Is there any way to make the QuickPost editor the default for non-Admins???
    3. For the most part my site is only open to members, but it does have some pages posts visible to the public (not logged in user). The DEFAULT setting for posts and pages is “Members ONLY”. Using the ‘backend’ WYSIWYG editor, the author can select t o whom the post will be visible (members only, non-members, etc.). Any post written with the QuickPost Widget is visible on the ‘public’ face of the site, i.e. to everyone. That’s a big problem for us. Any thoughts??

    You might want to look at the Quick Post Widget

    mauryg

    (@mauryg)

    I seem to be having the same problem. WP3.2.1 w/Suffusion 3.9.2 theme and BuddyPress 1.5.1. Placed QuickPostPage widget in its widget area along with a text widget holding some text. Created page “New Post” with shortcode [quick-post-page]. When I do a ‘view page’ from the admin panel I see a page with both the text widget information and post form. When I add this page to my menu and call it from the menu, I get ONLY the text info and NO Quick Post form. It looks like it is ignoring the shortcode.
    Any idea where I should look for the problem?

Viewing 10 replies - 46 through 55 (of 55 total)