Title: projectmanager_bugreport's Replies | WordPress.org

---

# projectmanager_bugreport

  [  ](https://wordpress.org/support/users/projectmanager_bugreport/)

 *   [Profile](https://wordpress.org/support/users/projectmanager_bugreport/)
 *   [Topics Started](https://wordpress.org/support/users/projectmanager_bugreport/topics/)
 *   [Replies Created](https://wordpress.org/support/users/projectmanager_bugreport/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/projectmanager_bugreport/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/projectmanager_bugreport/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/projectmanager_bugreport/engagements/)
 *   [Favorites](https://wordpress.org/support/users/projectmanager_bugreport/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[qTranslate] qtranslate is not compatible with wp version 3.8 or 3.8.1](https://wordpress.org/support/topic/qtranslate-is-not-compatible-with-wp-version-38-or-381/)
 *  [projectmanager_bugreport](https://wordpress.org/support/users/projectmanager_bugreport/)
 * (@projectmanager_bugreport)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/qtranslate-is-not-compatible-with-wp-version-38-or-381/#post-4939021)
 * Based on previous and current experience, it might be worth the effort searching
   for an alternative to qTranslate.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress HTTPS (SSL)] WP SSL 3.3.5 does not work with qTranslate 2.5.34](https://wordpress.org/support/topic/wp-ssl-335-does-not-work-with-qtranslate-2534/)
 *  Thread Starter [projectmanager_bugreport](https://wordpress.org/support/users/projectmanager_bugreport/)
 * (@projectmanager_bugreport)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/wp-ssl-335-does-not-work-with-qtranslate-2534/#post-3527869)
 * Hi lukelukeluke,
 * Mvied was indeed right: This is not an issue with WordPress HTTPS. The problem
   is on the side of qTranslate.
 * Regards
    Patrick
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress HTTPS (SSL)] WP SSL 3.3.5 does not work with qTranslate 2.5.34](https://wordpress.org/support/topic/wp-ssl-335-does-not-work-with-qtranslate-2534/)
 *  Thread Starter [projectmanager_bugreport](https://wordpress.org/support/users/projectmanager_bugreport/)
 * (@projectmanager_bugreport)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/wp-ssl-335-does-not-work-with-qtranslate-2534/#post-3527827)
 * Thought it was the first thing I did. Had it crossed out on my list. Apparently
   I ran over that step too fast. Well thanks any way.
 * Edit: Can you keep your test page online? I’ll reference it on the other plugin’s
   support page.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress HTTPS (SSL)] WP SSL 3.3.5 does not work with qTranslate 2.5.34](https://wordpress.org/support/topic/wp-ssl-335-does-not-work-with-qtranslate-2534/)
 *  Thread Starter [projectmanager_bugreport](https://wordpress.org/support/users/projectmanager_bugreport/)
 * (@projectmanager_bugreport)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/wp-ssl-335-does-not-work-with-qtranslate-2534/#post-3527817)
 * Problem reproduced again: Not fixed after update to WordPress HTTPS 3.3.6
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Simple Mail Address Encoder] V 1.5.2.1 merge subject and body](https://wordpress.org/support/topic/v-1521-merge-subject-and-body/)
 *  [projectmanager_bugreport](https://wordpress.org/support/users/projectmanager_bugreport/)
 * (@projectmanager_bugreport)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/v-1521-merge-subject-and-body/#post-3503189)
 * Problem seems to be still present in v1.5.2.2, see [http://wordpress.org/support/topic/ampersand-issue-body-parameter-not-evaluated?replies=1#post-4011490](http://wordpress.org/support/topic/ampersand-issue-body-parameter-not-evaluated?replies=1#post-4011490)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[ProjectManager] [Plugin: ProjectManager] Fatal error: Cannot access empty property](https://wordpress.org/support/topic/plugin-projectmanager-fatal-error-cannot-access-empty-property/)
 *  [projectmanager_bugreport](https://wordpress.org/support/users/projectmanager_bugreport/)
 * (@projectmanager_bugreport)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-projectmanager-fatal-error-cannot-access-empty-property/#post-1663550)
 * This happened for my projectmanager case, too.
    However, it first occurred right
   after upgrading from 2.9.7 to 3.0.3 (including the database migration thereafter).
 * The code works now, after I manually edited lib/core.php around line 932, where
   the error was caused.
 * In my edited version, that loop now looks like this:
 *     ```
       foreach ( $meta AS $m ) {
       				$key = sanitize_title($m->label);
       				if($key != null && $key != "")
       				{$dataset->{$key} = $m->value;}
       			}
       ```
   
 * So I just added the “`if`” conditions.
    The php interpreter cannot again be stuck
   in the assignment with an empty property.
 * Time for another Bugfix? Or my issue only?

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