spartacus fails to mirror htaccess

[garvinhicking]

Hi!

The XML is created just before the files are all mirrored, but it does happen in the same script call. But yes, the files are uploaded due to filesystem existence, not XML parsing or so.

I don't think there's a door being opened, but of course it's better to worry first rather than later, so thanks for your attention!

I would need to inspect how nginx handles files to be able to control s9y.org. I'll first check if it works on netmirror...

Regards,
Garvin

[Timbalu]

Whow, it is available on both now!!
Did this happen with your changes in github only, for these plugins having an htaccess, or did you need to add it also to the mirror, like suggested in my last (Edit) post?

BTW
Would my example still be a/the way to go?
What about checksum check for security?

[garvinhicking]

Hi!

Yes, saw that too. Great news. So I patched up the emerge_spartacus, and the XML should also contain said files. If that works properly as a download through spartacus, the next step would be to raise the plugin versions so that people can retrieve the new file.

It works now all through .htaccess, no change on a mirror server was required for this.

Checksum-checks could be added, but of course this is some work to implement...

Regards,
Garvin

[Timbalu]

I released the (old) fckeditor update to have a test Plugin for this tomorrow morning...
Cross your thumbs.

[Timbalu]

Its in the list and all loaded fine!
Now we can bump plugin versions to free this to the public.

If we have a plugin_root/.htaccess file, we can then purge img/.htaccess, which some plugins provide, since htaccess rules fall down the tree, don't they?!

(btw, did you get my beta test mail?)

[garvinhicking]

Hi!

OK. I bumped the version (except dpsyntaxhighlighter, that would be problematic). The img/.htaccess doesn't hurt, so I'd try to prevent extra work for me toc check this.

I just got your beta test mail and replied.

Regards,
Garvin

[Timbalu]

except dpsyntaxhighlighter, that would be problematic

Why?

[garvinhicking]

except dpsyntaxhighlighter, that would be problematic

Why?

The plugins version number is coupled with the dpssyntaxhighlight external plugin, if we raise one version we need to raise the external library one, or decouple it. Too much hassle.

Regards,
Garvin

[Zugschlus]

Hi,

sorry to bump this years old thread, but ...

Code: Select all

[4/2059]mh@ivanova:~ $ cat /home/mh-blog-zugschlus-de/s9y/serendipity/plugins/serendipity_plugin_twitter/.htaccess 
# Switch off reqrite engine, else documentation gets a wrong link
<Files .htaccess>
Allow from all
</Files>

<IfModule mod_rewrite.c>
RewriteEngine Off
</IfModule>

Is this .htaccess file the result of this thread? If so, it is supposed to end up in an actual installation?

If this is inteded to be there, please remember that in apache 2.4, the syntax of the ACLs has changed and these places need conditionals depending on the loaded module.

Greetings
Marc

[thh]

If so, it is supposed to end up in an actual installation?

It is - at least it does.

If this is inteded to be there, please remember that in apache 2.4, the syntax of the ACLs has changed and these places need conditionals depending on the loaded module.

Or mod_access_compat ...