Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by ceberlin

  1. Hi, thanks for your reply on this. Did I say I love this community already?

    My provider is not blocking allow_url_fopen, it is just off by default .So I could go and enable allow_url_fopen on my shared hosing. I am a bit over cautious about security (also because I do not consider myself being an excellent coder) and I like do disable as many powerful non-needed features as possible. Especially when dealing with new software (processwire) or complicated software (like my current Drupal installation, including the 103!!!! installed "beta"-type modules). That's why I asked.

    And if you search for allow_url_fopen, you find tons of warnings.

    I like the idea of this particular Module-Manager Module VERY much - it adds security, because it will make it really easy to keep my installation up-to-date.

    So I would be willing to try the module with allow_url_fopen enabled, but if curl would also work (yes, I have that plugin running) even better.

    An included download-link is not bad either.

  2. Hi,

    isn't allow_url_fopen a big security risk, if enabled? My povider suggests not to use that.

    Is there an alternative?

    For me, it would be good enough, if I would (like Drupal) receive an email, if modules, which I use, have updates, and an emergency email, if the module update is fixing a security bug. The cron would check that for me. (Or do we have that already and I had just screwed up my setup?)

  3. I like the idea to redirect external links to the new locations.

    But what is with internal links (coming from html text fields, for example). Wouldn't re-linking be much better than re-directing?

    Some thoughts:

    There could be some sort of internal-links list as a field where the user finds and sets all internal links he is intending to use on the page.

    And within the WYSIWYG editor the user would somehow be able to use a link-id instead of the real link, which is replaced by the real link on page output. Those links would be some kept up-to-date. Another benefit is that such an inventory could use a search for finding the right pages easily and fast (Drupal has such a module).

    A benefit of this would be that you could use that link-inventory to show an editor on the target page, which internal pages link to it.

    Or maybe a search & (optional !!) replace for links within the internal database. (Kind of mimicking Dreamweaver's behavior of keeping internal links within sites intact.)

    Or did I overlook a feature that is already existing in CW? - I am desperately missing some manual.

  4. @pete thanks for your expertise.

    just for Info: After a bad experience of the IPB support (I asked for something very

    specific - a pre-sale question about their shop and German Law - I just got a stupid

    reply how to run the demo instead of an answer to my question). I don't like them

    stealing my time. I was scared away and purchased xenforo. ???

    One good thought you have is why staying away from a single-logon.

    Also I need to check further how to override the PW logon, if needed.

    My idea is now to separate front end and backend users in a way that

    I use the PW login system for backend users:

    1. Backend users like admins will need to login to both system, which I think is ok.
    2. And a normal user needs to log in to xenforo to be able also to see some VIP content from PW also.

    If I want to hide PW content from normal users, I could try using the sessions, which xenforo creates....

    This is the route I am trying to use now.

    (I still need to install and get accustomed to PW als well as xenforo, but at least I have my first ideas now...)

    (If there is no mod or extension planned, this thread maybe belongs to the "how to" area of this board instead?)

    • Like 1
  5. Hello,

    I am in the early evaluation stage for PW.

    Coming from the Drupal 7 world and not being a software developer but coming

    from the design-side, these are my main goals for a new project:

    • design ...is everything:
      The normal webpages need to be as flexible as possible to design
      whereas is ok in the community area to have a more standard layout.
      PW is PERFECT for me, Drupal has limits (even with modules), a main
      reason for my unhappiness (and yes, I know how to make my own templates)
    • Organization:I am making a brochure style Webpage, PW is perfect here.
      (Drupal plays it's role when having millions of pages, which needs different
      organizations, like automatic menus, Taxonomy, views.
    • Developing speed.
      Drupal needs 10000000+ clicks for installation. And for every new project
      the same mess again. PW can be adapted easily.
    • Membership fun (forums, galleries, friending):
      Drupal is good, PW has nothing like that
    • E-Commerce: Drupal has unfinished stuff, PW nothing.

    I don't blame PW for its limitation with membership management and E-Commerce.

    Those limitation is also a strenght and beauty because PW is not feature-overloaded and easy

    to handle. (A reason for me to have arrived here!)

    And there are pefect solutions for that existing already, like the IP_Board and Magento.

    I am now thinking of combining the specialists in it's fields like PW and IP_Board

    to have the best of both worlds that would by far more manageable than Drupal

    with its modules.

    What about using the fine grained Bulletin Board membership membership management

    and use this to access users to PW content (and editors and admins to the PW backend).

    Isn't it easier to write a "bridge" module than adding membership features

    to PW and trying to re-invent the wheel? The IP_Board has a strong API for authentification.

    (This site is also using the IP_Board.)

    Which means that users register and login to the board to have access to

    PW privileges also (through synchronizing the user base or bypassing the PW auth).

    That would be perfectly bypassing the PW limit of not having a fine grained

    frontend user (users level1,2,3) and backend users (editors, admins).

    (I a same way e-commerce functionality could be added with another auth-"bridge".)

    Is there something in PW (a module?) I have overlooked that does this already?

    Otherwise I would like to post this here as a starting point for ideas and discussion.

    Thanks for reading all this. I am very curious about your opinions.


    Carl from Berlin

    • Like 1
  • Create New...