Thread

Does the exp:weblog:entry_form tag accept the “site=” parameter?  I just installed MSM for a client and everything is working besides the SAEF’s.  Anything wrapped in the SAEF tag is simply blank, with or without the site parameter.

RealityDesign,

What version and build of EE are you using?
Do you have any extensions installed?

Can we see what you have in your template?
Did you try with the example code from the User Guide?

1.6.8
Build: 20100121

Extensions:

Required Category Extension v1.0.2
Solspace UI v1.0.1
FieldFrame v1.4
SuperSearch v1.1.0
User v3.0.1
Parse Rating Stats v1.0.0
Stand Alone Entry Redirect v1.0.1
onSubmit v1.0.2
Stand Alone Entry Form Enctype v1.0.0
jQuery for Control Panel v1.1.1

I can’t really post the template here…it’s way too complex.  About 4,000 lines.  However, using just the example code from the user guide (and adding the “site=” parameter) provides the same result: a blank page.

At this point, I’m assuming you’ll tell me to start disabling extensions, but I can’t really do that since the “main site” in the MSM needs the extensions installed and is a live site.  I can try installing a backup of the sites on a test server and do it there, but that’s a real PITA.

Also, can you just answer my first question?

Does the exp:weblog:entry_form tag accept the “site=” parameter?

I’m sure the SAEF works fine in my MSM if I try to use it for a weblog that is contained within the current site, but the blank pages occur when trying to make a SAEF for weblogs on OTHER sites in the MSM.  This is exactly what an SAEF would do if the weblog you specified doesn’t exist, which makes me think the site parameter is in fact not working.

Hi, RealityDesign - the stand alone entry forms works only on the current site; the site= parameter is not supported.  You’re welcome to create a feature request to change that.

You might also have a look at the new SafeCracker; I believe, however, that is for EE 2 only, so you would need to upgrade to use it.

That’s extremely disappointing…not exactly sure what to tell my client now.  His sister site is essentially useless without it. =/

Now, without sounding too stupid here, can’t I just go in to the EE core (or related) files and find the portion of code that is responsible for the “site=” parameter in a different module, such as exp:weblog:entries?  Then just edit that bit of code and add it to the exp:weblog:entry_form module?  I haven’t looked at it yet, but that doesn’t seem like it would be that hard.  After all, the “site=” parameter works with so many other modules I don’t understand why it doesn’t work with this one.

And, not that it matters, but isn’t the entire point of MSM to have the ability to take content from one website and display/manipulate it on another?  Not supporting the site parameter in SAEF boggles my mind.  Did someone just get lazy or what?

Hi RealityDesign,

We can’t support modifying core files. Your best bet is definitely a feature request, and in the shorter term taking a look at Lisa’s recommendation.