Title: Multiside subdirectory
Last modified: December 8, 2018

---

# Multiside subdirectory

 *  [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/)
 * Hey Arno. Thanks for this **great plugin** !
 * I use Multisite-Subdirectory. If i use your plugin on common domain like domain.
   com, it works. But if i try your plugin on site like this domain.com/sub and 
   try to pick a date and time with jQuery UI Timepicker, nothing happens. I just
   get following:
 * > Warning!
   >  Some problems have been detected. Although you can still publish 
   > this rule, it may not work the way you expect. Starting Date/Time must be valid.
   > Ending Date/Time must be valid.
 * beside this, i get 404 error for: “timed-content/js/content-protector-datetime-
   i18n.js”
    But i get this error even on common domain. And here everything works
   well 🙂

Viewing 14 replies - 1 through 14 (of 14 total)

 *  Plugin Author [Arno Welzel](https://wordpress.org/support/users/awelzel/)
 * (@awelzel)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10962672)
 * I don’t know how to reproduce this error. I run a website as multidomain as subdirectory
   and there it works without problems. I also know of at least two other live sites
   in this configuration which work also without any problems.
 * Did you try to set up a test website without any other plugin just to be sure
   that it is really Timed Content and no any other plugin or specific setting?
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10962687)
 * Thanks for reply. I just tested it on another setup and you are right. It’s not
   reproduceable there. I made a plugin conflict test on my main-multisite setup.
   Still the above discribed error. Do you have an idea, which setting in WordPress
   setup may be responsible for causing such an error? After all, it can not be 
   due to other plugins, and as we recently learned, not even on the multisite.
 *  Plugin Author [Arno Welzel](https://wordpress.org/support/users/awelzel/)
 * (@awelzel)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10962698)
 * A detailed analysis of this problem would require full access to the affected
   WordPress installation to debug the website. But this is beyond the free support
   here, sorry.
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10962701)
 * I understand. Thank you anyway 🙂
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10963536)
 * Okay i found a solution. But this solution tells me, it’s an error of you plugin
   x).
    When i change site language from german to english, it’s working. If i change
   it back. It break again 🙂 Maybe you can replicate that 🙂
    -  This reply was modified 7 years, 6 months ago by [admin](https://wordpress.org/support/users/migup/).
 *  Plugin Author [Arno Welzel](https://wordpress.org/support/users/awelzel/)
 * (@awelzel)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10963539)
 * Since I run two multilingual websites (German/English) with this plugin and without
   any issues I don’t think so.
 * I use Multisite Language Switcher. What solution do you use for multilanguage
   use?
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10963542)
 * i use default wordpress settings to change language.
    wp-admin/options-general.
   php >> site language > from german to english (US) and back 🙂
 *  Plugin Author [Arno Welzel](https://wordpress.org/support/users/awelzel/)
 * (@awelzel)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10963543)
 * Works for me.
 * Edit: Ok, to be more precise – I don’t see any technical reason why a simple 
   language change should cause any problem like scripts getting not found any longer.
 * I can’t reproduce this on a fresh WordPress installation. I just install the 
   plugin – works. I change the language – works.
    -  This reply was modified 7 years, 6 months ago by [Arno Welzel](https://wordpress.org/support/users/awelzel/).
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10963563)
 * Tried through wp-admin/network/site-settings.php? with same result. Since i set
   
   WPLANG to de_DE it’s not working. Once i remove de_DE from WPLANG option, it 
   works again.
 * Wordpress 5.0
    PHP 7.2.
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10963565)
 * I can not explain it either. I’m just sending you my results while testing 🙂
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10963576)
 * Please check this video: [https://www.dropbox.com/s/a8bm49wqkmygql1/Language-change%20break%20plugin.mov?dl=0](https://www.dropbox.com/s/a8bm49wqkmygql1/Language-change%20break%20plugin.mov?dl=0)
   
   🙂
 *  Plugin Author [Arno Welzel](https://wordpress.org/support/users/awelzel/)
 * (@awelzel)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10967288)
 * Ok, I see – the problem is not a 404 error for “timed-content/js/content-protector-
   datetime-i18n.js” but the language specific date format.
 * I already work on a major update which uses a fixed date format which is independent
   of the current language – because language specific dates in the backend are 
   not a good idea anyway (also see [this support thread](https://wordpress.org/support/topic/dates-on-non-usa-websites/)).
   I hope to be able to publish the update this month. This should also solve your
   problem.
 * Until the update is available I can only recommend to input dates manually in
   the format “MM/DD/YYYY” and not to use the date selector at all. Sorry for the
   inconvenience and frohe Weihnachten ;-).
 *  Thread Starter [admin](https://wordpress.org/support/users/migup/)
 * (@migup)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-10968487)
 * Great to hear – thanks for your reply and this good news. I wish you a Merry 
   Christmas, too 🙂
 *  Plugin Author [Arno Welzel](https://wordpress.org/support/users/awelzel/)
 * (@awelzel)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-11110698)
 * I pushed an intermediate update which should avoid 404 errors in the backend.
   A major code refactoring is also in development and will hopefully be ready soon.

Viewing 14 replies - 1 through 14 (of 14 total)

The topic ‘Multiside subdirectory’ is closed to new replies.

 * ![](https://ps.w.org/timed-content/assets/icon-256x256.png?rev=2953069)
 * [Timed Content](https://wordpress.org/plugins/timed-content/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/timed-content/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/timed-content/)
 * [Active Topics](https://wordpress.org/support/plugin/timed-content/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/timed-content/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/timed-content/reviews/)

 * 14 replies
 * 2 participants
 * Last reply from: [Arno Welzel](https://wordpress.org/support/users/awelzel/)
 * Last activity: [7 years, 5 months ago](https://wordpress.org/support/topic/multiside-subdirectory/#post-11110698)
 * Status: not resolved