Forum Replies Created

Viewing 13 replies - 31 through 43 (of 43 total)
  • Thread Starter mkoenen

    (@mkoenen)

    I am sorry to say, it is not working for me.

    Again, and even in this new version, if I go to attachments.php and change the line wp_enqueue_script( 'bp-docs-attachments', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/attachments.js' ), array( 'media-editor', 'media-views', 'bp-docs-js' ), false, true );

    to

    wp_enqueue_script( 'bp-docs-attachments', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/attachments.js' ), array( 'media-editor', 'media-views' ), false, true );

    it works. Thus, just taking out , 'bp-docs-js' makes it work for me.

    Thread Starter mkoenen

    (@mkoenen)

    If you are running Buddypress Docs 1.8.4, FTP into your server, go to your plugins folder open buddypress-docs > includes > attachments.php.

    Find the line that reads wp_enqueue_script( 'bp-docs-attachments', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/attachments.js' ), array( 'media-editor', 'media-views', 'bp-docs-js' ), false, true );

    Change this line to `wp_enqueue_script( ‘bp-docs-attachments’, plugins_url( BP_DOCS_PLUGIN_SLUG . ‘/includes/js/attachments.js’ ), array( ‘media-editor’, ‘media-views’ ), false, true );

    Thread Starter mkoenen

    (@mkoenen)

    Here are some more detail:
    We are dealing with an activity stream that is translated so that all participants can read all comments in both English and French. Our issue is only with longer comments that are automatically abbreviated and need to be clicked (“read more”) on to read in their entirety.

    We have found that these comments can be translated by opening them in a new window or tab.

    However, even after translating them completely, reading them in both languages is not possible. Here is what we observed:

    If the original comment is in French and you are reading it in English and click on “read more”, the page reloads and loads only the comment so you can read it in its entirety. You then need to use the back button to navigate back to the activity stream (not ideal but not a problem).

    If the original comment is in English and you are reading it in French and click on “en afficher daventage” (“read more”), the whole comment opens up in the the same page but in English. French speakers are not able to read it. This is a problem for us.

    We hope that you can address this issue soon. Our international seminar on ebola is supposed to start on the 28th and we will attempt to have everything readable in both languages.

    It turns out we have the same issue.

    As hcroeze said, this only happens with docs that are set as a child of a parent doc.

    When I am on the docs page and look at the console, I see no error messages. Under ‘sources’ I see no docs javascripts loaded.

    Ditto after i click on one of the doc that results in a 404 page.

    I turned off plugins and changed the theme to twenty-fourteen and I still get the same error.

    Thread Starter mkoenen

    (@mkoenen)

    Unfortunately, it doesn’t resolve the issue.

    If I only make the change in components.php the upload works, but the “Access” problem is still there.

    If in addition, I make both changes (dependency and priority) in attachments.php neither uploads nor “Access” work.

    Thread Starter mkoenen

    (@mkoenen)

    So sorry about the confusion, I pasted the wrong line. So here it is again, hopefully a bit clearer.

    You said:
    – In wp-content/plugins/buddypress-docs/includes/component.php, find the line that begins wp_enqueue_script( 'bp-docs-edit-validation'. Change it to:

    wp_enqueue_script( 'bp-docs-edit-validation', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/edit-validation.js' ), array( 'jquery', 'bp-docs-js' ) );

    Doing this fixed it.

    You also said:

    – In wp-content/plugins/buddypress-docs/includes/attachments.php, find the line that begins wp_enqueue_script( 'bp-docs-attachments'. Change it to:

    wp_enqueue_script( 'bp-docs-attachments', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/attachments.js' ), array( 'media-editor', 'media-views', 'bp-docs-js' ), false, true );

    This breaks it again. It needs remain:

    wp_enqueue_script( 'bp-docs-attachments', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/attachments.js' ), array( 'media-editor', 'media-views' ), false, true );

    Please see also my note about “Access” option “Members of [group]” missing.

    If you want to see this in action, go to https://leadernetorg.staging.wpengine.com/groups/programs/sbcc-vldp-1430939895/docs/ You need to login to access the docs. Let me know if you did not get the login information.

    Thread Starter mkoenen

    (@mkoenen)

    When I updated BuddyPress Docs to the new version the “Add File” button stopped working for me again. It turns out only the later of the two changes is needed to make “Add File” work. why this was not obvious when I first applied the code change is still a mystery to me.

    Here is the summary:

    Changing wp-content/plugins/buddypress-docs/includes/component.php to read
    wp_enqueue_script( 'bp-docs-edit-validation', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/edit-validation.js' ), array( 'jquery', 'bp-docs-js' ) );
    fixed it.

    Changing wp-content/plugins/buddypress-docs/includes/attachments.php to read
    wp_enqueue_script( 'bp-docs-edit-validation', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/edit-validation.js' ), array( 'jquery', 'bp-docs-js' ) ); breaks it again. It needs to be:
    wp_enqueue_script( 'bp-docs-attachments', plugins_url( BP_DOCS_PLUGIN_SLUG . '/includes/js/attachments.js' ), array( 'media-editor', 'media-views' ), false, true );

    Now attachments.js and bp-docs.js load; edit-validation.js and idle.jsdo not load.

    We discovered a further issue. In the “Access” section, the option “Members of [group]” no longer exists. It just isn’t there. I don’t believe this is a new issue that occurred after the enqueue changes, we just had not noticed it. Disabling all other plugins did not solve the issue (so it’s not a Transposh issue).

    thank you again for your help.

    Thread Starter mkoenen

    (@mkoenen)

    Thank you, yes, it fixed the file upload issue!

    Unfortunately it did not fix the problem with the editing a doc.

    I have contacted the author of the Transposh plugin who responded that he is travelling and won’t be available for two weeks. I will let you know when I hear from him.

    Thank you again for responding so quickly and for fixing the upload issue.

    Thread Starter mkoenen

    (@mkoenen)

    Thank you for your help, Boone.

    I have given you access to our staging server. When I deactivate Transposh, the edit functionality clearly works.

    I am wondering if this could also be an issue with javascripts not loading (same as the “add file” issue described in a separate thread)? I see that with Transposh turned off, scripts are loading when I click the edit button and that they are not loading when Transposh is activated.

    Thread Starter mkoenen

    (@mkoenen)

    You are right, bp-docs.js is not loading.

    We also had difficulties with activity stream commenting not working. To make commenting work I started enqueuing the necessary scripts from my child theme functions file. It worked for comments.

    So I tried enqueueing bp-docs.js from my functions file. After doing so it loaded after attachments.js and before edit-validation.js and the button was still not working. I commented the line out again in order not to confuse things.

    We are not running SSL/https.

    I am giving you access to our staging environment.

    The makers of BuddyPress Multilingual have been promising an update to the plugin for nearly a year now. Since last December they have been promising the release “in a few weeks”. They have recently said they would have it “in a couple of weeks”. I am not holding my breath.

    I am looking for exactly the same thing.

    I am getting multiple notices but also a warning:
    Warning: trim() expects parameter 1 to be string, array given in /var/www/vhosts/blurtonline.com/httpdocs/wp-content/plugins/easy-nivo-slider/3rd-party/filosofo-custom-image-sizes.php on line 31

    So I changes line 31 from:

    $size_name = trim($size_name);

    to

    $size_name = trim('thumbnail');

    It removed the warning.

Viewing 13 replies - 31 through 43 (of 43 total)