Forums / Features Wish List / Potentially dangerous request.

Potentially dangerous request.

Results 1 to 4 of 4

22 Nov 2011, 19:38

hermes369

New Zenner

Join Date:: Dec 2006
Location:: Augusta, GA
Posts:: 74
Plugin Contributions:: 0

Potentially dangerous request.

I'd very much like to inject arbitrary php into banners and ez-pages. I use inject and arbitrary advisedly. I've found a way to accomplish this with ez-pages but, not yet with banners; though I'm betting the procedure is similar.

The more I look at what I've typed, the more I realize this might be a terrible idea. Perhaps it would be better if there were some hooks that could be added to protect from admin-user interference. Perhaps the introduction of types of users? A "store-owner" user and an "admin" user?

Please be gentle!

22 Nov 2011, 19:40

drbyte

Sensei

Join Date:: Jan 2004
Posts:: 63,513
Plugin Contributions:: 177

Re: Potentially dangerous request.

More importantly: WHY? What exactly are you trying to accomplish that leads you to use such terms?

As far as admin users go, v1.5.0 has per-user admin access control.

23 Nov 2011, 02:47

hermes369

New Zenner

Join Date:: Dec 2006
Location:: Augusta, GA
Posts:: 74
Plugin Contributions:: 0

Re: Potentially dangerous request.

I think I was being over-dramatic. Mainly, I want to have access to the <head> of specific ez-pages and to be able to add php directly to the text-area in the admin area's ez-pages and in the banner manager.

My specific problem is integrating phpSmug to make a photo/video gallery inside an easy page and for a slider that's in a banner on the main page of the store. Not every page of the store needs this, so I'd like to be able to target only those pages that need it.

Cool to learn about the super-user! Thanks!

23 Nov 2011, 04:53

drbyte

Sensei

Join Date:: Jan 2004
Posts:: 63,513
Plugin Contributions:: 177

Re: Potentially dangerous request.

You can do custom javascript <head>-insertions for ez-pages, and other pages, by following the built-in conventions.